FlowchartAI MCP vs Lucid
A side-by-side look at the FlowchartAI MCP and Lucid MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FlowchartAI MCPData VisualizationFlowchartAI MCP connects AI assistants to editable flowcharts. Generate diagrams from text or an image, revise an existing diagram with natural-language instructions, list and read saved diagrams, inspect task and version history, and export editable draw.io XML or JSON. Saved diagrams open in the FlowchartAI web editor for further editing and PNG/SVG rendering. The hosted Streamable HTTP endpoint supports OAuth with PKCE and scoped API keys. Generation and edits use the existing account allowance or Credits, with per-task spending caps and account/key budgets. The public repository is MIT licensed; the hosted service requires a FlowchartAI account.51GoodAuth: oauth 2.0Verdict: choose FlowchartAI MCP for data visualization work; choose Lucid for data visualization over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose FlowchartAI MCP when
- You need dedicated capabilities in the Data Visualization domain.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
DATABASE_URL, BETTER_AUTH_SECRET, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, OPENROUTER_API_KEY.
Choose Lucid when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F FlowchartAI MCP | |
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 51/100 · Good | 41/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | DATABASE_URLBETTER_AUTH_SECRETGOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRETOPENROUTER_API_KEY |
Tools & capabilities
FlowchartAI MCP tools
No tool names declared yet. Check the project README from the listing page.
Lucid 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.
FlowchartAI MCP
No confirmed install command for FlowchartAI MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Lucid
{
"mcpServers": {
"lucid": {
"url": "https://mcp.lucid.app/mcp"
}
}
}
Frequently asked questions
FlowchartAI MCP is categorized under Data Visualization and uses an install path we have not confirmed yet. Lucid belongs to Data Visualization and uses a remote HTTP/SSE transport. Pick FlowchartAI MCP for data visualization work and Lucid 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. FlowchartAI MCP has no confirmed install command yet — follow its own setup instructions.
FlowchartAI MCP is listed as a paid service. Auth: oauth 2.0. Lucid 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 flowchartai-mcp and lucid as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FlowchartAI MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 44 GitHub stars. Lucid has 41/100 (Fair) with 3 views, 0 installs and 3 GitHub stars.