Lucid vs Chartforge
A side-by-side look at the Lucid and Chartforge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lucid for data visualization work over a hosted endpoint; choose Chartforge for data visualization as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Lucid when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a remote HTTP/SSE transport.
Choose Chartforge when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CHARTFORGE_API_KEY, CHARTFORGE_API_URL. - You want tools like
generate_chart, refine_chart, list_styles.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 41/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | CHARTFORGE_API_KEYCHARTFORGE_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Lucid | View Chartforge |
Tools & capabilities
Lucid tools
No tool names declared yet. Check the project README from the listing page.
Chartforge tools 3
generate_chartGenerate a stunning, publication-quality chart or diagram from a natural language description. Returns a PNG image.refine_chartModify an existing chart. Provide the chart ID from a previous generation and describe what to change.list_stylesList available chart style presets with descriptions.
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.
Lucid
{
"mcpServers": {
"lucid": {
"url": "https://mcp.lucid.app/mcp"
}
}
}
Chartforge
{
"mcpServers": {
"chartforge": {
"command": "npx",
"args": [
"chartforge-mcp"
],
"env": {
"CHARTFORGE_API_KEY": "YOUR_CHARTFORGE_API_KEY_HERE",
"CHARTFORGE_API_URL": "YOUR_CHARTFORGE_API_URL_HERE"
}
}
}
}
Frequently asked questions
Lucid is categorized under Data Visualization and uses a remote HTTP/SSE transport. Chartforge belongs to Data Visualization and uses a local stdio subprocess. Pick Lucid for data visualization work and Chartforge 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.
Lucid has no declared pricing — check the project's own site. Chartforge 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 lucid and chartforge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lucid has a quality signal of 41/100 (Fair) with 3 views, 0 installs and 3 GitHub stars. Chartforge has 51/100 (Good) with 2 views, 0 installs and 0 GitHub stars.