Microcharts vs Metabase
A side-by-side look at the Microcharts 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 Microcharts 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 Microcharts 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
find_microchart, get_microchart, render_microchart.
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 | 69/100 · Great | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 204 | 49,815 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Microcharts | View Metabase |
Tools & capabilities
Microcharts tools 3
find_microchartRank microcharts chart types against a plain-language question about data ("is it trending?", "error budget", "part to whole"). Returns candidates with the reason each matched. Start here when you know the question, not the chart.get_microchartFull wiring detail for one chart by slug: import paths, its props plus the shared props, data shape, best/avoid guidance, a copy-runnable example, and `sample` — the example as JSON props you can pass straight to render_microchart.render_microchartRender a chart to a finished, self-contained SVG (styles embedded) plus its generated alt text — for surfaces that can't run React. Pass the series as `data`; put other props (value, target, curve, color, width) in `props`. Each chart takes its own data shape — get_microchart returns a valid `sample` to adapt.
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.
Microcharts
{
"mcpServers": {
"ganapativs-microcharts": {
"command": "npx",
"args": [
"-y",
"@microcharts/mcp"
]
}
}
}
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
Microcharts 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 Microcharts 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.
Microcharts is listed as free. Auth: no auth required. Metabase is listed as free. 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 ganapativs-microcharts and metabase as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Microcharts has a quality signal of 69/100 (Great) with 4 views, 0 installs and 204 GitHub stars. Metabase has 41/100 (Fair) with 1 views, 0 installs and 49,815 GitHub stars.