
Glyphic
io.github.MS-Teja由 GitHub 帳號 MS-Teja 發布v1.0.2更新於 Oct 24, 2026
Generate 18 diagram types from structured JSON natively. Built for LLMs and agents.
概覽
讓助理把結構化 JSON 轉成 18 種型別的圖表,輸出 SVG、PNG 或 React Flow JSON。
- 可以做什麼
- Glyphic 以具型別的 JSON 而非手繪方式產生圖表。模型輸出嚴格的節點與邊(或實體、提交等)結構,繪製前先做驗證,伺服器回傳可縮放 SVG、高解析度 PNG 或 React Flow JSON。它支援 18 種圖表型別,包括架構圖、時序圖、ERD、UML 類別圖、狀態機、流程圖、甘特圖、時間軸、桑基圖、Git 圖、心智圖、圓餅圖、象限圖、使用者旅程、看板、C4、矩形樹狀圖與自由畫布,並提供主題、樣式預設、長寬比取景、字型與 FontAwesome 圖示。
- 適用情境
- 當助理需要把圖表當成可重複、可編輯的產物,而不是一次性手寫 SVG 時適用,特別適合大型圖表、文件與 CI 流程,或把圖表產生嵌入產品。也適合希望用一次經過驗證的工具呼叫完成圖表產生的代理與 LLM 應用開發者。
- 執行需求
- 透過 npx 以 stdio 方式在本機執行 npm 套件 @glyphicjs/mcp-server,需要 Node.js。未宣告驗證、環境變數或標頭。也可作為函式庫使用,或自架為 HTTP 服務。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Glyphic,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
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:
For Cursor, Claude Desktop, VS Code, Windsurf, and Antigravity, add it to your client's MCP config:
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
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:
- 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|). - 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. - 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
See the full comparison + benchmarks.
Features
- 🧩 18 diagram types behind one validated schema — see them all.
- 🎨 Theming — built-in presets (
"theme": "dark", pluslight/pastel/mono) or a full custom palette. Theming guide. - 🖌️ Styles — visual personality presets:
"style": "compact"(default),clean,minimal, or hand-drawnsketch. 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 viacustomIcons. - 📐 Real layout —
elkjs+d3compute 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.
Monorepo architecture
A pnpm + Turborepo monorepo of three open-source libraries.
Adding a new diagram type is one entry in packages/core/src/registry.ts plus a schema and a layout adapter — see CONTRIBUTING.
Documentation
- 📚 Documentation home
- 🖼️ Examples gallery — every type, rendered
- 🧩 Diagram types reference — schema for all 18 types
- 🖌️ Styles & aspect-ratio framing
- 🎨 Theming, fonts & icons
- 🛠️ Core API
- 🔌 MCP server
- 🤝 Contributing
Blog
- 📌 Introducing Glyphic: diagrams as data for LLMs and agents — start here
- 🏗️ Why Glyphic is infrastructure, not an app
- 🎨 Everything Glyphic can do
- ⚖️ Glyphic vs. the alternatives
- 🤖 Why AI-drawn diagrams don't scale
- 🔬 Is the AI-diagram comparison fair? A note on method
Support
- 🐛 Issues & feature requests — github.com/MS-Teja/Glyphic/issues
- 📚 Documentation — docs home
- ❤️ Sponsor development — github.com/sponsors/MS-Teja
License
LICENSE — FSL / MIT.
來源:README.md,提交 ed79edb
工具
0版本歷史
1- v1.0.2最新Sep 16, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。