DrillFlow vs LetDraw
A side-by-side look at the DrillFlow and LetDraw MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DrillFlow for data visualization work as a local process; choose LetDraw 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 DrillFlow when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DRILLFLOW_TOKEN, DRILLFLOW_API_URL. - You want tools like
publish_diagram, publish_mermaid, read_diagram.
Choose LetDraw when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LETDRAW_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 55/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | DRILLFLOW_TOKENDRILLFLOW_API_URL | LETDRAW_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View DrillFlow | View LetDraw |
Tools & capabilities
DrillFlow tools 3
publish_diagramPublishes a DrillFlow document, returns the share URL.publish_mermaidConverts a Mermaid flowchart (subgraphs → subflows) and publishes it.read_diagramReads a published diagram back as its document — share URL, `@handle/name` address or slug.
LetDraw 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.
DrillFlow
{
"mcpServers": {
"drillflow": {
"command": "npx",
"args": [
"-y",
"drillflow-mcp"
],
"env": {
"DRILLFLOW_TOKEN": "YOUR_DRILLFLOW_TOKEN_HERE",
"DRILLFLOW_API_URL": "YOUR_DRILLFLOW_API_URL_HERE"
}
}
}
}
LetDraw
{
"mcpServers": {
"letdraw": {
"command": "npx",
"args": [
"-y",
"@letdraw/mcp"
],
"env": {
"LETDRAW_TOKEN": "YOUR_LETDRAW_TOKEN_HERE"
}
}
}
}
Frequently asked questions
DrillFlow is categorized under Data Visualization and uses a local stdio subprocess. LetDraw belongs to Data Visualization and uses a local stdio subprocess. Pick DrillFlow for data visualization work and LetDraw 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.
DrillFlow has no declared pricing — check the project's own site. LetDraw has no declared pricing — check the project's own site. Auth: api key required. 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 drillflow and letdraw as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DrillFlow has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. LetDraw has 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.