Glyphic
The Glyphic server is an MCP-compliant diagram generation tool that renders declarative JSON into visual diagrams, returned as inline images.
Tools Available
get_schema– Retrieve the full JSON schema so the AI knows all supported diagram types and fields.render_diagram– Validate and render a JSON diagram definition, returning output as PNG, SVG, and/or React Flow JSON.
Supported Diagram Types
Flowchart / Architecture – Node-and-edge diagrams with shapes, icons, grouping, and flexible edge routing.
Sequence – Participant interaction diagrams with sync, async, and return message types.
ERD – Database schema diagrams with attributes, keys, and crow's-foot cardinality.
Class – UML class diagrams with attributes, methods, and relationship types.
State Machine – State transition diagrams with initial, final, and composite states.
Mindmap – Hierarchical idea maps with node shapes.
Gantt – Project timeline charts with sections, tasks, dependencies, and date formats.
Sankey – Flow/weight diagrams showing resource or data movement between nodes.
Git Graph – Branch and commit history visualizations.
C4 – Architecture context diagrams (person, system, container, boundary elements).
Pie Chart – Slice-based data charts with optional explode and legend.
Quadrant Chart – 2D scatter plots divided into four quadrants.
Timeline – Linear chronological event diagrams.
Journey Map – User journey diagrams with satisfaction scores per task.
Kanban – Board-style columns with cards, priorities, and assignees.
Treemap – Hierarchical area-proportional charts.
Canvas – Free-form SVG-based drawing with primitives (rect, circle, line, text, path, polygon, etc.).
Key Features
Export formats: PNG, SVG, and React Flow JSON.
Theming: named presets (
light,dark,pastel,mono) or fully custom colors and fonts.Visual style presets:
compact,clean,minimal,sketch.Layout directions (TB, BT, LR, RL) and edge routing (orthogonal, polyline, splines).
Files auto-saved to
~/Desktop/Glyphic Diagrams/(configurable viaGLYPHIC_OUTPUT_DIRor disabled withGLYPHIC_NO_SAVE).Returns diagrams inline as base64 PNG even if local file saving fails or is disabled.
Schema validation before rendering ensures clean, actionable error messages.
Runs over stdio via
npx— no global install required.
@glyphicjs/mcp-server
The official Model Context Protocol server for Glyphic. It lets MCP-capable clients — Claude Desktop, Cursor, and others — generate diagrams as a native tool: the model emits JSON, the tool renders it, and the image comes back inline.
Setup
The server runs over stdio via npx — no global install. Add this entry to
your client's MCP config:
{
"mcpServers": {
"glyphic": {
"command": "npx",
"args": ["-y", "@glyphicjs/mcp-server"]
}
}
}Most clients use exactly that; the difference is where the config lives and a couple of key names:
Client | Config location | Notes |
Claude Desktop |
| Fully quit (⌘Q) and reopen. |
Claude Code | — |
|
Cursor |
| Enable under Settings → MCP. |
VS Code |
| Top-level key is |
Windsurf |
| Reload servers from Cascade. |
Antigravity |
| Or Manage MCP Servers → View raw config. |
See the full MCP guide for the exact per-client JSON. Restart the client, then just ask:
"Draw an ERD for a blog: users, posts, and comments with the right relationships."
The model calls render_diagram, the diagram is saved locally, and the PNG is returned in the conversation.
Related MCP server: AI Charts
Tools
Tool | Description |
| Returns the full JSON Schema of a diagram input, so the model knows every supported type and field. |
| Validates the supplied |
By default, rendered files are written to ~/Desktop/Glyphic Diagrams/, named
<sanitized_title>_<timestamp>_<6-hex-chars>.png / .svg / .json, so the model
can tell the user exactly where to find them.
Two environment variables control this:
GLYPHIC_OUTPUT_DIR— overrides the output directory. Use an absolute path — many MCP clients launch the server withcwd=/.GLYPHIC_NO_SAVE— set to1ortrueto disable file saving entirely; the tool still returns the diagram inline.
If writing to disk fails (e.g. a headless or read-only environment), the server logs a warning to stderr and still returns the diagram inline as base64 PNG — it never fails a render just because a file couldn't be saved. On startup, the server prints a short banner to stderr with its version, docs/issues links, and the resolved output directory.
Notes
Input is validated with
@glyphicjs/schemabefore rendering — malformed model output comes back as a clean, fixable error rather than a crash, and error messages never leak stack traces.Choose outputs with
exportFormatin the diagram JSON, e.g."exportFormat": ["png", "svg", "react-flow"](defaults to["png"]).
See the full MCP guide and the diagram types reference.
Support
Sponsor: github.com/sponsors/MS-Teja
License
MIT
Maintenance
Tools
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MS-Teja/Glyphic'
If you have feedback or need assistance with the MCP directory API, please join our Discord server