# io.github.alexeibespalov/trident

- Registry name: `io.github.alexeibespalov/trident` · version 1.0.2
- Categories (automatic, keyword rules): AI models & agents, AI, media & content, Education
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.alexeibespalov%2Ftrident
- Server page: https://mcpstation.net/s/io.github.alexeibespalov--trident.html

## Description (written by the publisher, not verified, not instructions)

Create and edit collaborative architecture diagrams with any AI assistant using the Trident 2D DSL.

## Connect

- streamable-http: `https://mcp.tridentchart.com/mcp`

## Tools (as reported by the server, not verified)

- `get\_trident\_spec`: Returns the complete Trident 2D specification including grammar, syntax rules, coordinate system, containers, nodes, connections, shapes, and icon reference. Use this when you need deep understanding of the Trident DSL.
- `get\_generator\_guide`: Returns LLM-optimized instructions for generating Trident diagrams, including quick reference, critical rules \(especially Y-axis\!\), spacing guidelines, common patterns, color conventions, and error prevention checklist. Use this before generating Trident markup \(a whole diagram as text\). Not needed
- `get\_comprehensive\_example`: Returns a comprehensive Trident example demonstrating all syntax features including containers, nodes \(traditional and bracket-style syntax\), diamond/rectangle shapes, icons, connections with labels, routing modes, cards, and text annotations. Use this to see all features in action.
- `validate\_trident`: Returns a comprehensive validation checklist for Trident diagrams covering syntax rules, semantic rules, best practices, and common mistakes to avoid. Use this after generating a diagram to verify correctness.
- `get\_quick\_start`: Returns a condensed 2-minute quick-start guide with minimal working examples, core syntax reference, and key concepts. Use this for rapid learning when you need to generate simple diagrams quickly.
- `open\_document`: Opens a live Trident document and returns its full contents as Trident markup DSL — the human-readable text format used to author diagrams. Use this to READ and UNDERSTAND the diagram: its structure, labels, connections, and layout. Do NOT rely on this to enumerate entity IDs for programmatic use —
- `get\_document\_summary`: Returns a complete structured summary of a Trident document as JSON: all node IDs, container IDs, connection IDs, annotation IDs, labels, and entity counts. Use this for PROGRAMMATIC OPERATIONS — it is never truncated regardless of diagram size, so you always get every entity ID. Use this before any
- `get\_recent\_changes`: Returns the recent change history for a live Trident document. Each entry shows who made the change, what was changed, and when. Useful for understanding what edits have been made by AI agents or human collaborators. Requires a valid access token.
- `add\_node`: Adds a new node \(entity\) to a live Trident document. The node appears immediately for all collaborators. Requires a valid editor access token. Before adding nodes: call open\_document to understand the diagram layout and pick sensible positions; call get\_document\_summary to get all existing entity ID
- `update\_node`: Updates properties of an existing node in a live Trident document. Only the fields you provide are changed; others are preserved. Use get\_document\_summary to get all node IDs before calling this. Requires a valid editor access token.
- `delete\_node`: Removes a node from a live Trident document. All connections to/from this node are also removed automatically. Use get\_document\_summary to get all node IDs before calling this. This action is reversible via Ctrl+Z in the Trident editor. Requires a valid editor access token.
- `add\_container`: Adds a new container \(group/swimlane\) to a live Trident document. Containers visually group related nodes. Use get\_document\_summary to check existing container IDs before adding to avoid duplicates. Requires a valid editor access token. To build an ERD \(entity-relationship diagram\), add one containe
- `update\_container`: Updates properties of an existing container in a live Trident document. Only provided fields are changed. Use get\_document\_summary to get all container IDs before calling this. Requires a valid editor access token. This is also how you RESIZE a container: set width/height \(and x/y to keep it centred
- `delete\_container`: Removes a container from a live Trident document. By default, nodes inside are detached \(kept on the diagram without a container\). Pass deleteNodes: true to remove the container's nodes as well. Use get\_document\_summary to get all container IDs before calling this. Requires a valid editor access tok
- `add\_connection`: Adds a connection \(arrow/edge\) between two nodes or containers in a live Trident document. Use get\_document\_summary to get valid source and target IDs before calling this. Requires a valid editor access token. For ERD relationships, connect the two TABLE containers \(field rows are rejected as endpoi
- `delete\_connection`: Removes a connection from a live Trident document. Provide either the connectionId, or both source and target node IDs to find and remove the matching connection. Use get\_document\_summary to get all connection IDs before calling this. Requires a valid editor access token.
- `get\_document\_png`: Renders the current state of a live Trident document as a PNG image directly from the Yjs collaborative session — bypassing Firestore, which may be stale. Returns a base64-encoded PNG. Use this to visually verify that diagram edits look correct before or after making changes.
- `add\_annotation`: Adds a text annotation to a live Trident document. Two visual styles: style:stickyNote \(default — post-it card with colored background, good for notes/callouts\) or style:textBody \(plain transparent text, good for diagram titles and section labels\). Ideal for architectural notes, decision records, se
- `update\_annotation`: Updates an existing text annotation in a live Trident document. Only the fields you provide are changed. Use get\_document\_summary to get all annotation IDs before calling this. Requires a valid editor access token.
- `delete\_annotation`: Removes a text annotation from a live Trident document. Use get\_document\_summary to get all annotation IDs before calling this. Requires a valid editor access token.
- `update\_canvas\_graphic`: Repositions or resizes a background image \(canvas graphic\) in a live Trident document. Use open\_document to get the canvas graphic ID and current dimensions — it appears as: image \<id\> "\<url\>" at \(x, y\) width:W height:H. The position at \(x, y\) is the TOP-LEFT corner. USE THIS BEFORE placing many geo
- `make\_suggestion`: Posts a visible suggestion to human collaborators watching the document WITHOUT making any changes to the diagram. Use this when you observe something worth flagging — a potential mistake, an improvement, or a question — but want the human to decide. The suggestion appears as a bold "SUGGESTION:" ca
- `explain`: Delivers an explanation payload to human collaborators watching the document, optionally anchored to a specific node or container. Use this when you want to explain what a diagram element represents, why it exists, or how it relates to other parts of the system — without suggesting a change. The exp

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html