MCP Mermaid vs Metabase
A side-by-side look at the MCP Mermaid and Metabase MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Mermaid for data visualization work as a local process; choose Metabase for data visualization. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Mermaid when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
generate_mermaid_diagram.
Choose Metabase when
- You need dedicated capabilities in the Data Visualization domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 65/100 · Great | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
Tools & capabilities
MCP Mermaid tools 1
generate_mermaid_diagramGenerate mermaid diagram and chart with mermaid syntax dynamically. Mermaid is a JavaScript based diagramming and charting tool that uses Markdown-inspired text definitions and a renderer to create and modify complex diagrams. The main purpose of Mermaid is to help documentation catch up with development.
Metabase tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Mermaid
{
"mcpServers": {
"hustcc-mcp-mermaid": {
"command": "npx",
"args": [
"-y",
"mcp-mermaid"
]
}
}
}
Metabase
No confirmed install command for Metabase yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Mermaid is categorized under Data Visualization and uses a local stdio subprocess. Metabase belongs to Data Visualization and uses an install path we have not confirmed yet. Pick MCP Mermaid for data visualization work and Metabase for data visualization.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Metabase has no confirmed install command yet — follow its own setup instructions.
MCP Mermaid is listed as free. Auth: no auth required. Metabase has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hustcc-mcp-mermaid and metabase as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Mermaid has a quality signal of 65/100 (Great) with 3 views, 0 installs and 642 GitHub stars. Metabase has 39/100 (Fair) with 0 views, 0 installs and 49,592 GitHub stars.