LetDraw vs Glyphic
A side-by-side look at the LetDraw and Glyphic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose LetDraw for data visualization work as a local process; choose Glyphic 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 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.
Choose Glyphic 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
get_schema, render_diagram.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 45/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | LETDRAW_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 10 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View LetDraw | View Glyphic |
Tools & capabilities
LetDraw tools
No tool names declared yet. Check the project README from the listing page.
Glyphic tools 2
get_schemaReturns the JSON schema of the DiagramInput payload to help the AI understand supported diagram types and properties.render_diagramRenders a declarative JSON diagram into a visual representation. The input MUST conform to the DiagramInput schema.
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.
LetDraw
{
"mcpServers": {
"letdraw": {
"command": "npx",
"args": [
"-y",
"@letdraw/mcp"
],
"env": {
"LETDRAW_TOKEN": "YOUR_LETDRAW_TOKEN_HERE"
}
}
}
}
Glyphic
{
"mcpServers": {
"ms-teja-glyphic": {
"command": "npx",
"args": [
"-y",
"@glyphicjs/mcp-server"
]
}
}
}
Frequently asked questions
LetDraw is categorized under Data Visualization and uses a local stdio subprocess. Glyphic belongs to Data Visualization and uses a local stdio subprocess. Pick LetDraw for data visualization work and Glyphic 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.
LetDraw has no declared pricing — check the project's own site. Auth: api key required. Glyphic is listed as free. Auth: no auth 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 letdraw and ms-teja-glyphic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LetDraw has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Glyphic has 65/100 (Great) with 8 views, 0 installs and 10 GitHub stars.