archdiagram
MCP server for generating architecture diagrams with official vendor icons from natural language descriptions. Provides tools to validate specs, render diagrams, search icon catalog, and list available services.
README
archdiagram
Turn an architecture description into an editable diagram whose nodes are the official vendor service icons (Azure App Service, AKS, Key Vault, S3, GKE, ...) - not a flowchart of labelled boxes.
A coding agent (Cursor, Claude Code, Codex) translates a natural-language architecture into a small JSON spec; the deterministic Python core renders that spec to:
| Format | Best for | Vendor icons | Editable after import |
|---|---|---|---|
.pdf |
Lucidchart visual fidelity, handoff, printing | baked in, always render | no (Lucid embeds as image) |
.drawio |
editing in draw.io / diagrams.net | native stencils or embedded | yes |
.vsdx |
Visio / Lucid editable import | embedded PNG glyphs | yes |
Lucid note: Lucid does not map draw.io's named vendor stencils or its
img/lib/...icon references, so those render blank on import..drawio/.vsdxtherefore embed icons (--drawio-mode portable) to maximise render success, and the PDF is the reliable icons-always-render deliverable for Lucid.
Gallery
Rendered from the specs in examples/ - same engine, real vendor icons.
| Azure | AWS | GCP |
|---|---|---|
![]() |
![]() |
![]() |
Design constraints
- Core engine = pure Python stdlib. No graphviz, no browser, no third-party Python deps.
Spec validation is hand-rolled (no
jsonschema)..vsdxis written withzipfile+xml. - Python 3.11+. Tests use stdlib
unittest. - Optional, isolated, non-stdlib deps:
mcpSDK - only insidemcp_server/.- Node +
@resvg/resvg-js- rasterise icons to PNG; used by.vsdx(embedded glyphs) and.pdf. If absent,.vsdxfalls back to labelled boxes and.pdferrors with an install hint. - Node +
pdfkit+svg-to-pdfkit- SVG -> PDF for.pdf.
- Vendor icons are not committed. Fetch them with
tools/download_icons.py.
Quick start
# 1. (optional) fetch vendor icons into the local cache
python -m tools.download_icons --vendors azure,aws,gcp,kubernetes
# 2. (optional) install the Node rasterise/pdf bridge
cd node && npm install && cd ..
# 3. render a spec
python -m archdiagram.cli render examples/sample_spec.json --format pdf -o out/arch.pdf
python -m archdiagram.cli render examples/sample_spec.json --format drawio -o out/arch.drawio --drawio-mode portable
python -m archdiagram.cli render examples/sample_spec.json --format vsdx -o out/arch.vsdx
Spec format
{
"title": "Web platform",
"direction": "LR",
"groups": [{ "id": "app", "label": "Application tier", "vendor": "azure" }],
"nodes": [
{ "id": "web", "service": "azure.app_service", "label": "Web App", "group": "app" },
{ "id": "aks", "service": "azure.aks", "label": "AKS", "group": "app" },
{ "id": "kv", "service": "azure.key_vault", "label": "Key Vault" }
],
"edges": [
{ "source": "web", "target": "aks", "label": "http" },
{ "source": "aks", "target": "kv" }
]
}
service is "<vendor>.<service_key>". Unknown services degrade gracefully to a labelled box.
Layout
Node positions are computed by a deterministic, hand-rolled layered layout (no graphviz). Provide
explicit x/y on a node to override the computed position.
Use from an AI agent
This repo is built to be driven by agentic AI tools (Cursor, Claude Code/Desktop, Codex, ...) straight from Git. Pick either path:
1. As a skill
Clone the repo and point your agent at skill/SKILL.md. It
teaches the agent the spec schema, catalog lookup, and render commands so it can
go from a natural-language architecture to rendered files. See also
AGENTS.md.
git clone https://github.com/bharathgnana/archdiagram.git
cd archdiagram && python -m tools.download_icons
2. As an MCP server
pip install "archdiagram[mcp]"
python -m mcp_server.server # stdio transport
Exposes validate_spec, render_diagram, search_catalog, and list_catalog
tools. A sample client config is in examples/mcp.json
(drop it into .cursor/mcp.json or claude_desktop_config.json).
Repository layout
archdiagram/ pure-Python core (spec, layout, catalog, emitters)
mcp_server/ optional MCP server (only place the `mcp` SDK is used)
node/ optional Node bridge (resvg rasterise + svg->pdf)
tools/ icon downloader + icon source map
skill/ SKILL.md for agentic AI tools
examples/ sample specs + mcp.json
tests/ stdlib unittest suite
Tests
python -m unittest discover -s tests
Contributing
Anyone can clone, install (pip install -e .), and use it. To propose changes,
fork and open a pull request - see CONTRIBUTING.md for the
dev setup and workflow.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。


