Skip to main content
Glama

AtomicViz Diagrams

Server Details

Interactive diagrams you can collapse, regroup and focus: architecture, dependencies, org charts

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
briandiloreto/AtomicViz
GitHub Stars
26
ChatGPT
–
Claude
–

TDQS

A4.8/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is nothing to confuse it with. Its description also draws explicit boundaries (relationship diagrams and architecture maps, not numeric charts), further ruling out misselection.

Naming Consistency5/5

The single name 'create_diagram' follows a clean verb_noun snake_case convention that matches the domain. There is no mixing of styles to evaluate, and the name reads unambiguously.

Tool Count4/5

The server's domain is a single action, such as rendering a diagram, so one tool is defensible rather than an oversight; the tool's rich parameter surface for nodes, edges, groups, and nesting carries the whole feature set. It is still a thin surface, with no separate tool for editing or validating a diagram, which keeps it just short of a perfect fit.

Completeness4/5

The tool covers the full lifecycle of a diagram request: nodes, parent rows, groups, edges with labels and styles, hover text, links, colors, and initial collapse state. Since the server is stateless and stores nothing, the only real gap is incremental editing; regeneration by calling the tool again is a workable substitute.

Available Tools

1 tool
create_diagramCreate an interactive diagramA
Read-only
Inspect

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.

Inputs: nodes (required), edges, title.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.