
Interactive diagrams you can collapse, regroup and focus: architecture, dependencies, org charts
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Creates an interactive diagram in the conversation from nodes and edges you supply. Use it when the user asks to draw, diagram, map or visualize how the parts of something relate: system architecture, services and the calls between them, data models, dependency trees, workflows, organizations, knowledge maps. Not for charts of numeric data. In the diagram the user can collapse and expand boxes, regroup at each level of nesting, focus on an item and what connects to it, show clusters and cycles, and search, hide and export. The server checks the diagram and stores nothing. STRUCTURE: every node has a unique 'id'. A node with no 'parent' is drawn as a box of its own; a node WITH a 'parent' is drawn as a ROW inside its parent's box (an endpoint inside a service, a column inside a table) and the parent can be collapsed. 'group' (top-level nodes only) draws a labelled boundary around nodes, nested with '/': 'AWS/VPC' puts the node in a VPC box inside an AWS box. If you use groups, give EVERY top-level node a group: the views that draw groups as closed or stacked boxes are offered only when no node is left out. Edges run between any two nodes, rows included; give an edge a short 'label' only when the relation is not obvious ('HTTPS', 'publishes'). Optional per node: 'description' (shown on hover; add one only where the label is not enough), 'link' (an https URL, opened on double-click), 'color', 'kind': 'field' for an attribute-style row, 'collapsed': true to start folded. Optional per edge: 'color', 'style' ('dashed' for async or optional, 'dotted' for weak). Keep it legible: prefer grouping and nesting over hundreds of top-level boxes; use color for a category, not decoration.
Diagram title, shown as its name.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http diagrams https://atomicviz.com/mcp
Creates an interactive diagram in the conversation from nodes and edges you supply. Use it when the user asks to draw, diagram, map or visualize how the parts of something relate: system architecture, services and the calls between them, data models, dependency trees, workflows, organizations, knowledge maps. Not for charts of numeric data. In the diagram the user can collapse and expand boxes, regroup at each level of nesting, focus on an item and what connects to it, show clusters and cycles, and search, hide and export. The server checks the diagram and stores nothing. STRUCTURE: every node has a unique 'id'. A node with no 'parent' is drawn as a box of its own; a node WITH a 'parent' is drawn as a ROW inside its parent's box (an endpoint inside a service, a column inside a table) and the parent can be collapsed. 'group' (top-level nodes only) draws a labelled boundary around nodes, nested with '/': 'AWS/VPC' puts the node in a VPC box inside an AWS box. If you use groups, give EVERY top-level node a group: the views that draw groups as closed or stacked boxes are offered only when no node is left out. Edges run between any two nodes, rows included; give an edge a short 'label' only when the relation is not obvious ('HTTPS', 'publishes'). Optional per node: 'description' (shown on hover; add one only where the label is not enough), 'link' (an https URL, opened on double-click), 'color', 'kind': 'field' for an attribute-style row, 'collapsed': true to start folded. Optional per edge: 'color', 'style' ('dashed' for async or optional, 'dotted' for weak). Keep it legible: prefer grouping and nesting over hundreds of top-level boxes; use color for a category, not decoration.
| Argument | Type | Description |
|---|---|---|
| edges | array | |
| nodes* | array | |
| title | string | Diagram title, shown as its name. |
{
"type": "object",
"required": [
"nodes"
],
"properties": {
"edges": {
"type": "array",
"items": {
"type": "object",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Target node id."
},
"from": {
"type": "string",
"description": "Source node id."
},
"color": {
"enum": [
"gray",
"red",
"orange",
"yellow",
"green",
"teal",
"blue",
"purple",
"pink"
],
"type": "string"
},
"label": {
"type": "string",
"maxLength": 120
},
"style": {
"enum": [
"solid",
"dashed",
"dotted"
],
"type": "string"
}
},
"additionalProperties": false
},
"maxItems": 20000
},
"nodes": {
"type": "array",
"items": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Unique id; edges and parents refer to it."
},
"kind": {
"enum": [
"node",
"field"
],
"type": "string",
"description": "'field' draws an attribute-style row; default 'node'."
},
"link": {
"type": "string",
"maxLength": 2000,
"description": "https URL, opened on double-click."
},
"color": {
"enum": [
"gray",
"red",
"orange",
"yellow",
"green",
"teal",
"blue",
"purple",
"pink"
],
"type": "string"
},
"group": {
"type": "string",
"maxLength": 400,
"description": "Boundary path for a top-level node, nested with '/', e.g. 'AWS/VPC'. If any top-level node has one, give one to all of them."
},
"label": {
"type": "string",
"maxLength": 200,
"description": "Text drawn on the node. Defaults to the id."
},
"parent": {
"type": "string",
"description": "Id of the node this one is drawn inside, as a row."
},
"collapsed": {
"type": "boolean",
"description": "Start with this node folded."
},
"description": {
"type": "string",
"maxLength": 2000,
"description": "Shown on hover."
}
},
"additionalProperties": false
},
"maxItems": 5000,
"minItems": 1
},
"title": {
"type": "string",
"maxLength": 200,
"description": "Diagram title, shown as its name."
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 21, 2026.