Glyphic

io.github.MS-TejaPublished by GitHub account MS-Tejav1.0.2Updated Oct 24, 2026

Generate 18 diagram types from structured JSON natively. Built for LLMs and agents.

Overview

AI-generated overview

Lets an assistant turn structured JSON into diagrams in 18 types, returning SVG, PNG, or React Flow JSON.

What you can do
Glyphic renders diagrams from typed JSON rather than freehand drawing. The model emits a strict schema of nodes and edges (or entities, commits, and similar), which is validated before rendering, and the server returns scalable SVG, high-resolution PNG, or React Flow JSON. It covers 18 diagram types including architecture, sequence, ERD, UML class, state machines, flowcharts, Gantt, timelines, Sankey, Git graphs, mindmaps, pie, quadrant, user journeys, Kanban, C4, treemaps, and a freeform canvas, with theming, style presets, aspect-ratio framing, fonts, and FontAwesome icons.
When to use it
Useful when an assistant should produce diagrams as a repeatable, editable artifact instead of one-off hand-written SVG, especially for large diagrams, documentation and CI pipelines, or embedding diagram generation in a product. It suits agent and LLM-app builders who want diagram generation behind a single validated tool call.
Requirements
Runs locally over stdio via npx from the npm package @glyphicjs/mcp-server; Node.js is required. No authentication, environment variables, or headers are declared. It can also be used as a library or self-hosted as an HTTP service.
Before you install
The server writes rendered diagram files (SVG, PNG) and returns React Flow JSON, so output paths and content should be reviewed. No credentials, payments, or third-party data sharing are declared. The README states input validation, SVG escaping, and size limits are built in.

Installation

In SourceWeft

  1. Open Glyphic in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Glyphic

A diagram is data, not a drawing.

Your model describes the diagram as typed JSON; Glyphic renders it — deterministic SVG & PNG across 18 types, validated before it draws, with no DSL and no headless browser. Diagram infrastructure for LLMs and agents that you own and build on.

[npm version] [mcp-server npm version] [npm downloads] [License: FSL / MIT] [Sponsor]

Live playground · Quick Start · Examples Gallery · Documentation · 18 Diagram Types

[Sketch architecture diagram] [Freeform canvas dashboard]


Quick Start

Glyphic gives an LLM structured data in and hands you a finished diagram out. Use it three ways.

1. MCP server — add to your AI agent in 30 seconds

It runs over stdio via npx, no install:

bash
# Claude Codeclaude mcp add glyphic -- npx -y @glyphicjs/mcp-server

For Cursor, Claude Desktop, VS Code, Windsurf, and Antigravity, add it to your client's MCP config:

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

Then just ask: "Draw an ERD for a blog with users, posts, and comments." The model emits the JSON, calls the tool, and the rendered diagram appears inline. See the MCP setup guide.

2. Library

bash
npm install @glyphicjs/core @glyphicjs/schema
typescript
import { processDiagram } from "@glyphicjs/core";import { writeFileSync } from "node:fs";
const result = await processDiagram({  type: "architecture",  title: "Web App",  nodes: [    { id: "web", label: "Web App", shape: "rounded", icon: "fab-react" },    { id: "api", label: "API", shape: "hexagon", icon: "fas-bolt" },    { id: "db", label: "PostgreSQL", shape: "database", icon: "fas-database" }  ],  edges: [    { source: "web", target: "api", label: "REST" },    { source: "api", target: "db", label: "SQL" }  ]});
writeFileSync("diagram.png", result.png);   // Buffer (high-res PNG)writeFileSync("diagram.svg", result.svg);   // string (scalable SVG)console.log(result.reactFlow);              // interactive React Flow JSON

See the Core API reference.

3. Self-hosted HTTP API

Need it behind your own endpoint? Glyphic can be self-hosted as an HTTP service that wraps the exact same engine — same schema in, same SVG/PNG/React Flow out — so your product or platform can generate diagrams without shipping the library to every client.

Who it's for

  • Agent & LLM-app builders — expose diagram generation as a single tool call and let the model describe it, not draw it.
  • Platform teams — embed diagram generation directly in your product behind one validated schema.
  • CI & docs pipelines — deterministic, byte-identical, versionable output with no Chromium to install or babysit.
  • React developers — get interactive React Flow JSON out of the box, not just static images.

What

Glyphic is infrastructure for generating diagrams from structured data. You give it a strict, semantic JSON document — arrays of nodes and edges, or entities, or commits — and it returns a polished diagram as:

  • SVG — pure, scalable vector markup (accessible: role="img" + <title>).
  • PNG — high-resolution raster, rendered natively via Rust (@resvg/resvg-js).
  • React Flow JSON — nodes/edges mapped for an interactive React Flow canvas.

It supports 18 diagram types (architecture, sequence, ERD, UML class, state machines, flowcharts, Gantt, timelines, Sankey, Git trees, mindmaps, pie, quadrant, user journeys, Kanban, C4, treemaps, and a freeform canvas) behind a single validated schema.

Why

Yes — a modern LLM can draw a clean six-box flowchart as raw SVG. Go ask one; for a single throwaway diagram, that's the right tool. This isn't a bet that models "can't draw."

The problem is that a drawn SVG is a dead picture. It comes out different every generation, it falls apart exactly where real diagrams live — many nodes and later edits — and to change one box you regenerate the whole thing and it drifts. Glyphic treats the diagram as data: your model describes what it means as typed JSON, and a real engine renders it. Three reasons that holds up no matter how good the model gets:

  1. A machine-authoring contract, not a DSL. The input is a strict Zod schema. Malformed model output comes back as a precise, fixable error before anything renders — so generate → validate → fix → render loops are trivial. DSLs like Mermaid parse-or-crash on a single typo (-->|label|).
  2. Deployable as infrastructure. Layout is computed by real graph engines (elkjs, d3-hierarchy/d3-sankey) and SVG is rasterized to PNG by Rust (@resvg/resvg-js) — no DOM, no headless browser, no Chromium. It runs in a CI job, a Lambda, an agent loop, or a Docker container as a normal Node dependency. This stays true regardless of model capability.
  3. Cheap and intact at scale. Hand-drawing a large diagram means emitting thousands of coordinate tokens — slow, costly, and liable to blow the model's output limit and truncate into a broken render. Your model emits compact semantic JSON instead; the heavy geometry is generated deterministically.

And because a real engine owns the layout, the diagram scales and stays editable: it nests clusters and routes edges around obstacles where hand-placed SVG turns into diagonal lines cutting through boxes, its output is byte-identical (versionable, snapshot-testable), and the JSON stays a source of truth you can diff and re-render — not a house of cards of absolute coordinates.

[The same 44-node architecture: a frontier model's one-shot raw SVG (edges tangled diagonally through boxes) above Glyphic's rendering of the identical JSON (nested tiers, routed edges)]
The same 44-node spec. Top: a current frontier model asked for raw SVG — the boxes are fine, but the edges cut diagonally through shapes and the result can't be edited without regenerating it. Bottom: Glyphic renders the identical JSON — nested tiers, edges routed around obstacles, still an editable source of truth.
Method: both produced by the same model (Claude Opus 4.8) from one brief — the top by asking it to hand-write SVG in a single pass; the bottom by asking it to emit Glyphic's typed JSON, then rendering with @glyphicjs/core (ELK layout + resvg, no browser). Same author, same content — only the draw-vs-describe boundary differs.

How it compares

FeatureGlyphicClaude ArtifactsMermaidD2
Input formatTyped JSON (Zod schema)Natural language → SVGText DSLText DSL
Renders without a browser✅ Rust (resvg)N/A (cloud-only)❌ Puppeteer/Chromium✅ Go binary
Model-agnostic✅ Any JSON-capable LLM❌ Claude only✅✅
Schema validation✅ Zod + fixable errors❌❌ Parse-or-crash❌
Native MCP server✅ @glyphicjs/mcp-serverN/A (built-in to Claude)❌❌
React Flow output✅ Interactive nodes/edges❌❌❌
Deterministic output✅ Byte-identical❌⚠️ Mostly✅
LicenseFSL → Apache-2.0ProprietaryMITMPL-2.0

See the full comparison + benchmarks.

Features

  • 🧩 18 diagram types behind one validated schema — see them all.
  • 🎨 Theming — built-in presets ("theme": "dark", plus light / pastel / mono) or a full custom palette. Theming guide.
  • 🖌️ Styles — visual personality presets: "style": "compact" (default), clean, minimal, or hand-drawn sketch. Styles guide.
  • 📺 Aspect-ratio framing — auto-fits diagrams to clean 16:9 / 9:16 frames (or set "aspectRatio"), by padding — never cropping.
  • 🔤 Fonts — any Google Font ("theme": { "fontFamily": "Outfit" }) or your own .ttf.
  • 🖼️ Native icons — drop in any FontAwesome icon ("icon": "fas-database", "icon": "fab-aws") or your own SVG via customIcons.
  • 📐 Real layout — elkjs + d3 compute nesting (VPCs/clusters), crow's-foot/UML markers, and edge routing around obstacles — staying clean at the node counts where hand-placed SVG tangles into diagonals through boxes.
  • ⚡ Native PNG — Rust rasterization, no headless browser.
  • ♿ Accessible output — every SVG ships with role="img" and a <title>.
  • 🔒 Safe by construction — strict input validation, SVG output escaping/sanitization, and size limits to resist malicious input.
  • 🧪 Multiple outputs — SVG, high-res PNG, and React Flow JSON from one call.

Supported Diagrams

18 first-class types — explore them in the Examples Gallery and the Diagram Types reference.

Architecture (nested VPCs/clusters)C4 contextFlowchart
SequenceState machineERD (crow's-foot)
UML ClassMindmapGantt
TimelineUser JourneyKanban
PieQuadrantSankey
Git graphTreemapCanvas (freeform SVG)

Monorepo architecture

A pnpm + Turborepo monorepo of three open-source libraries.

PackageWhat it is
@glyphicjs/schemaThe pure Zod validation layer — the LLM-facing contract. Validate model output before rendering.
@glyphicjs/coreThe engine: layout adapters, scene graph, SVG rendering, and rasterization.
@glyphicjs/mcp-serverOfficial Model Context Protocol server — exposes Glyphic as a native tool to Claude Desktop / Cursor.

Adding a new diagram type is one entry in packages/core/src/registry.ts plus a schema and a layout adapter — see CONTRIBUTING.

Documentation

Blog

Support

License

LICENSE — FSL / MIT.


Give your AI structured data. Let Glyphic handle the drawing.

Source: README.md at commit ed79edb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.