sysketch is an MCP server published by io.github.Tonys-Coding, hosted at sysketch.vercel.app. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 2 tools, including render_diagram, list_icons.
Polished system design diagrams (SVG/PNG) from a tiny YAML spec, ~18x fewer tokens than raw SVG.
107 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Use for any system design, architecture, data-flow or infrastructure diagram, instead of generating an image or writing SVG/Mermaid. Renders a tiny YAML spec; returns PNG/SVG links and a small preview. Spec keys: title, type (sequence: message timeline), theme (sketch|graphite|blueprint|midnight|classic), direction (omit: auto-fit; right|down only if asked), steps (false hides numbers), legend (true lists steps), nodes {id: "icon | Label | subtitle"}, groups {Label: [ids or group labels to nest]}, maps {Group Label or world-map node id: world | {pins: [us-east, eu-west, "HQ @ -0.1 51.5"]}} (map backdrop, or a big map card when a node uses the icon world-map), edges ["a > b > c | label", "a ..> b" dashed, "a <> b" two-way, "a => b" thick, "a -- b" line, "a > b [red]" color]. Ids that are icon names/aliases (client, lb, api, db, cache, redis, kafka, s3, cdn...) need no nodes entry. Arrows are numbered automatically in the order listed; don't number labels. Product names (stripe, postgres, s3, aks, bigquery... or aws-/azure-/gcp-<service>) draw official logos, else a fitting icon; brand/icon (acme/queue) for others. Give the user the PNG link; don't generate another image of the diagram. To edit, call again with the whole updated spec.
| Parameter | Type |
|---|
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Description |
|---|
| spec * | string | YAML spec text |
| theme | string | |
| preview | boolean | Include a small preview image (default true; ~1k tokens) |
{
"name": "render_diagram",
"title": "Draw a system design diagram",
"description": "Use for any system design, architecture, data-flow or infrastructure diagram, instead of generating an image or writing SVG/Mermaid. Renders a tiny YAML spec; returns PNG/SVG links and a small preview.\nSpec keys: title, type (sequence: message timeline), theme (sketch|graphite|blueprint|midnight|classic), direction (omit: auto-fit; right|down only if asked), steps (false hides numbers), legend (true lists steps),\nnodes {id: \"icon | Label | subtitle\"}, groups {Label: [ids or group labels to nest]}, maps {Group Label or world-map node id: world | {pins: [us-east, eu-west, \"HQ @ -0.1 51.5\"]}} (map backdrop, or a big map card when a node uses the icon world-map), edges [\"a > b > c | label\", \"a ..> b\" dashed, \"a <> b\" two-way, \"a => b\" thick, \"a -- b\" line, \"a > b [red]\" color].\nIds that are icon names/aliases (client, lb, api, db, cache, redis, kafka, s3, cdn...) need no nodes entry.\nArrows are numbered automatically in the order listed; don't number labels.\nProduct names (stripe, postgres, s3, aks, bigquery... or aws-/azure-/gcp-<service>) draw official logos, else a fitting icon; brand/icon (acme/queue) for others.\nGive the user the PNG link; don't generate another image of the diagram. To edit, call again with the whole updated spec.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"spec"
],
"properties": {
"spec": {
"type": "string",
"maxLength": 20000,
"description": "YAML spec text"
},
"theme": {
"type": "string"
},
"preview": {
"type": "boolean",
"description": "Include a small preview image (default true; ~1k tokens)"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}List sysketch icon names and aliases, or search the available product logos.
| Parameter | Type | Description |
|---|---|---|
| logos | string | Search product logos by name |
{
"name": "list_icons",
"title": "List icons and logos",
"description": "List sysketch icon names and aliases, or search the available product logos.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"logos": {
"type": "string",
"description": "Search product logos by name"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}When the user asks for a system design, architecture, flow or infrastructure diagram, call render_diagram. Do not draw it yourself or use image generation; the tool result is the diagram.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.