独立运营 · 不出售排名位置  · 我们怎么评估工具 →
Anclum 提交收录
A

ayeshLK/archsmith

本站为独立目录,非该工具官网;下方信息取自其公开仓库。

ArchSmith turns a validated JSON description of a layered system architecture into a clean, consistent SVG diagram. (原文为英文)

7 ★ 本站实测 · 核对 2026-11-19

装之前:命令归属未核实,仅作参考展示 · 许可证 Apache-2.0

第一步(仅参考,归属未核实):npm install -g @archsmith/cli

★ 7·更新 2026-11-16
在 GitHub 查看 ↗直链 · 无中转页

我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →

★ 数取值
7 ★ · ayeshLK/archsmith · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
来源明细
收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
评分构成
综合分 300 · 7 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 ayeshLK/archsmith;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
README 原文(英文,未翻译) · 在 GitHub 读完整 README →

# ArchSmith

以下摘录自该仓库的 README(片段)

= 20">
ArchSmith turns a validated JSON description of a layered system architecture into a clean, consistent SVG diagram. Feed it a structured document (an IR — intermediate representation), get back a diagram in a fixed, opinionated house style: no per-diagram layout decisions, no hand-drawn boxes, no drift between one architecture doc and the next.
It's built as a library first, a CLI on top of that, and an MCP server on top of that — so it's just as easy for a human to run archsmith render as it is for an AI agent to call it as a tool.
The session above builds ticket-booking — the same reference example used throughout this README — with no hand-written JSON, saved as author-demo.archsmith.json .
> [!NOTE]
> ArchSmith is pre-1.0 — the schema and API may still change (diagram-schema.json itself is marked "first pass, expect revision"). See releases for what's shipped in each version.
## Why
Drawing an architecture diagram by hand is slow and doesn't scale: every new diagram means re-deciding box shapes, colors, spacing, and layout from scratch, and keeping a whole set of diagrams visually consistent — a real "house style" — is a losing battle once more than one person is producing them. It's harder still now that agents, not just humans, increasingly need to produce these diagrams: an agent can't open a drawing tool and drag boxes around, but it can absolutely produce structured JSON.
Just asking an LLM to draw an SVG diagram directly doesn't fix this either — it trades manual inconsistency for a different kind, where the same request can come out looking different depending on the day, the model, or the prompt. ArchSmith separates those two concerns instead: an agent (or a human) does the interpretation — turning a sketch or a description into a valid structured document — and hands it to ArchSmith for deterministic rendering. Same input, same output, every time, with the house style (spacing, colors, text wrapping, box shapes) enforced by the renderer rather than re-decided per diagram — down to embedding the exact font text was measured against, so a diagram looks the same on any machine viewing it, not just the one that rendered it.
## How
ArchSmith currently supports one diagram convention: a layered/swimlane style that lays out a system's architecture as five columns, left to right:
1. Inbound Actors — who or what calls into the system (end users, other apps, partner integrations).
2. Ingress — the API gateway/edge layer requests come in through.
3. Core Platform — the backend itself: API-management/identity concerns, the actual business-logic services, an optional domain-model layer, and the platform's own databases/files ("Systems of Record").
4. Egress — the gateway layer through which the platform calls out to other systems.
5. External Systems — downstream dependencies reached via egress, grouped into named clusters.
Every color, box shape, spacing rule, and text-wrapping decision in that layout was pixel-measured against real reference diagrams, not guessed — see packages/schema/README.md for how the sub-layer/color palette is governed as it grows.
Describing an architecture is just picking what goes in each column and writing it down: a title, a short description, and — for items with a role worth flagging, like "the primary database" or "only reached via egress" — a colored dot or a small pill tag. No coordinates, no manual layout, no font-size or spacing decisions to make; the renderer works out box sizes, text wrapping, and alignment from the content alone. See the IR shape below for the actual JSON structure, and Quick start to render one.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/zh/s/ayeshlk-archsmith/)
来源
awesome · https://github.com/ayeshLK/archsmith
按领域浏览
MCP 服务
Traction
7 ★
收录来源
3 个独立来源
收录于
今天

更多 MCP 服务器

全部 6,555 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引