All servers / Other / AtomicViz Diagrams
AtomicViz Diagrams
Interactive diagrams you can collapse, regroup and focus: architecture, dependencies, org charts
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://atomicviz.com/mcp · Registry name: com.atomicviz/diagrams
Score 100 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Inputs explained | 15 / 15 | |
| Speed | 15 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (0.7 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: atomicviz-diagrams 1.2.0
- Tools offered: 1 · Parameters with a plain description: 3 of 3
- Official registry entry last updated: 2026-11-21
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
create_diagram3 of 3 parameters describedCreates 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
Tested by ConnectATD. Spotted a mistake? Tell us.