antigravity-drawio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_smart_diagramC | Generate a professionally themed, auto-laid-out diagram without calculating manual pixel coordinates. |
| generate_c4_diagramB | Generate an official C4 architecture diagram (Context, Container, or Component view) with actors, systems, and boundaries. |
| generate_er_diagramA | Generate a relational database ER schema diagram with tables, primary/foreign keys, types, and cardinalities. |
| generate_sequence_diagramC | Generate a UML sequence diagram with lifelines, sync/async call arrows, and return messages. |
| patch_diagramA | Surgically patch an existing diagram: add/delete/update nodes, rewire edges, group into containers, or highlight paths. |
| beautify_diagramC | Beautify any existing diagram by running topological auto-layout, resolving overlapping links, and applying modern themes. |
| analyze_diagramB | Analyze diagram topology: extracts entry points, sinks, feedback cycles, bottlenecks, and critical execution paths. |
| create_diagramB | Create a new .drawio XML diagram file with nodes and edges at specified coordinates. |
| export_diagramB | Export a .drawio XML diagram to PNG, SVG, PDF, or JPEG using desktop CLI. |
| open_in_drawioB | Open a .drawio diagram file directly in the local Draw.io Desktop GUI app. |
| parse_diagramB | Parse a .drawio XML file and extract structured nodes, edges, and page metadata. |
| convert_mermaid_to_drawioC | Convert a Mermaid JS graph definition string into native .drawio XML. |
| validate_diagramA | Audit a .drawio diagram file for node collisions and text boundary overflows. |
| resolve_diagram_collisionsC | Auto-resolve node collisions in a .drawio diagram by shifting overlapping coordinates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each generator targets a distinct diagram type, and lifecycle tools like create, patch, parse, export, and validate have clear boundaries. Minor overlap exists between beautify_diagram and resolve_diagram_collisions, both dealing with layout/overlap fixes.
Tools consistently use snake_case verb-first names such as generate_*, create_diagram, patch_diagram, and validate_diagram. open_in_drawio and convert_mermaid_to_drawio break the strict verb_noun pattern but remain predictable.
14 tools cover generation, editing, layout, analysis, validation, conversion, export, and GUI opening without redundancy. The count is well-scoped for a diagramming server.
The set covers diagram creation, parsing, patching, layout, validation, conversion, export, and opening, which is a complete workflow. It lacks an explicit file deletion/list operation, but that is a minor gap outside core diagramming.