Glyphic

What MS-Teja/Glyphic MCP server does

MS-Teja/Glyphic MCP server lets an AI agent describe a diagram as typed JSON and submit it for rendering. The input follows a DiagramInput schema with diagram-specific properties, such as nodes and edges for graph-based diagrams or other structured collections for timelines, charts, and related formats.

The renderer supports 18 diagram types, including architecture diagrams, ERDs, sequence diagrams, UML class diagrams, state machines, flowcharts, Gantt charts, timelines, Sankey diagrams, Git trees, mindmaps, pie charts, quadrants, user journeys, Kanban boards, C4 diagrams, treemaps, and freeform canvases.

The underlying engine produces SVG and PNG output and can also return React Flow JSON for interactive node-and-edge views. Rendering is handled natively rather than through a headless browser, so the project is suited to local agent workflows, CI jobs, and applications that need generated diagram assets.

How it works

The agent first calls get_schema to inspect the accepted DiagramInput structure. It can then construct a JSON diagram and call render_diagram. The render request must conform to the returned schema; invalid input is rejected during validation instead of being drawn as an incomplete result.

Glyphic calculates layout from semantic diagram data and generates the visual output. This keeps the JSON as a source representation that can be changed, compared, and rendered again. The output is intended to be deterministic and does not require Chromium or another browser runtime.

Setup and configuration

MS-Teja/Glyphic MCP server runs through npx and does not require a separate installation step. A direct stdio configuration is:

{
  "mcpServers": {
    "glyphic": {
      "command": "npx",
      "args": ["-y", "@glyphicjs/mcp-server"]
    }
  }
}

The README provides configuration examples for Claude Desktop, Cursor, VS Code, Windsurf, and Antigravity. Claude Code can add the same server with claude mcp add glyphic -- npx -y @glyphicjs/mcp-server.

No API key or external service credential is specified for the MCP setup. The repository also documents a separate library and a self-hosted HTTP API, but those are different usage modes from the MCP server.

Tools and capabilities

• get_schema: returns the JSON schema for DiagramInput so an agent can form valid requests.
• render_diagram: accepts a schema-conforming declarative diagram and renders it.
• Generates native SVG and high-resolution PNG output.
• Supports React Flow JSON output through the Glyphic engine.
• Handles 18 diagram categories through one validated input model.
• Supports built-in theme presets and custom palettes in the broader Glyphic input model.

Limitations and notes

The render request must follow the DiagramInput schema. Agents should inspect get_schema before generating unfamiliar diagram types or properties. The provided material does not specify an HTTP endpoint, authentication scheme, environment variables, or runtime configuration for the MCP package.

MS-Teja/Glyphic MCP server is focused on rendering structured diagrams; it does not expose general-purpose image editing or free-form drawing tools. Although the project can emit React Flow JSON, the MCP listing specifically identifies schema inspection and diagram rendering as its exposed tools.