mcp server

trident

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

Description as published by the maintainer. Source

• version 1.0.2
• active

active — Most recent push to the repository was 2026-07-12.

What this server can do

23 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

add_annotation(token, agentId, userName, annotation, action_explanation)

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, section labels, or TODO markers. Appears immediately for all collaborators. Requires a valid editor access token. Required: token, agentId, annotation.

add_connection(token, agentId, userName, connection, action_explanation)

Adds a connection (arrow/edge) between two nodes in a live Trident document. Use get_document_summary to get valid source and target node IDs before calling this. Requires a valid editor access token. Required: token, agentId, connection.

add_container(token, agentId, userName, container, action_explanation)

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. Required: token, agentId, container.

add_node(node, token, agentId, userName, action_explanation)

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 IDs so you can avoid duplicates. IMPORTANT: if this node belongs inside a container, pass node.container on THIS call — do NOT create the node without a container and reparent it later via update_node. Orphaned nodes appear immediately to all live collaborators and create unnecessary visual churn. Required: token, agentId, node.

delete_annotation(token, agentId, userName, annotationId, action_explanation)

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. Required: token, agentId, annotationId.

delete_connection(token, source, target, agentId, userName, connectionId, action_explanation)

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. Required: token, agentId.

delete_container(token, agentId, userName, containerId, deleteNodes, action_explanation)

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 token. Required: token, agentId, containerId.

delete_node(token, nodeId, agentId, userName, action_explanation)

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. Required: token, agentId, nodeId.

explain(token, agentId, entityId, userName, explanation)

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 explanation appears in the UI attributed to you. Does NOT mutate the diagram. Requires a valid viewer or editor access token. IMPORTANT: this tool automatically pauses (3–15 s, proportional to explanation length) before returning, so the human has time to read. Do NOT add your own artificial delays between explain calls — the pacing is built in. Required: token, agentId, userName, explanation.

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.

get_document_png(token)

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. Required: token.

get_document_summary(token)

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 bulk update, delete, or enumeration task. To read and understand the diagram as a human-readable diagram, use open_document instead. Requires a valid access token. Required: token.

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 any Trident diagram.

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.

get_recent_changes(limit, since, token)

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. Required: token.

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.

make_suggestion(token, agentId, entityId, userName, 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:" callout in the UI with a radar pulse animation on your presence dot for 10 seconds. Does NOT mutate the diagram. Requires a valid viewer or editor access token. Required: token, agentId, userName, suggestion.

open_document(token, agentId, userName)

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 — the DSL can be very large and the output may be truncated. To get a complete, structured list of all entity IDs and counts, use get_document_summary instead. Requires a valid access token. Required: token.

update_annotation(token, agentId, changes, userName, annotationId, action_explanation)

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. Required: token, agentId, annotationId, changes.

update_canvas_graphic(token, agentId, changes, userName, canvasGraphicId, action_explanation)

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 geographically-positioned nodes: if the background map is small (e.g. width < 700), scale it up so nodes have room to breathe and do not overlap. Requires a valid editor access token. Required: token, agentId, canvasGraphicId, changes.

update_container(token, agentId, changes, userName, containerId, action_explanation)

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. Required: token, agentId, containerId, changes.

update_node(token, nodeId, agentId, changes, userName, action_explanation)

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. Required: token, agentId, nodeId, changes.

validate_trident(diagram)

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.

Last successful function declaration observed on 2026-08-13. Source: https://mcp.tridentchart.com/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on 2026-08-13. Source: https://mcp.tridentchart.com/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Where to get it

• Repository — https://github.com/alexeibespalov/tridentpublic
• npm: trident-mcp
• Remote endpoint (streamable-http) — https://mcp.tridentchart.com/mcp

Related, by what their authors tagged them

• ai.adeu/adeu — last commit 2026-08-03, shares gemini-cli-extension
  Automated DOCX Redlining Engine
• ai.dataecho/mcp — last commit 2026-07-04, shares gemini-cli-extension
  Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory.
• Minds: Synthetic Market Research Panels — last commit 2026-08-01, shares gemini-cli-extension
  Run AI market research: synthetic customer panels for concept testing, message testing, segments.
• Vaaya — last commit 2026-08-06, shares gemini-cli-extension
  Pay-per-call agent superpowers: media/video gen, product demos, research, GTM, scraping, compute.
• Wiplash — last commit 2026-07-31, shares gemini-cli-extension
  Discover Wiplash and manage owned agents with human OAuth.
• Remote Desktop Commander — last commit 2026-08-06, shares gemini-cli-extension
  Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
• app.turnale/turnale — last commit 2026-08-03, shares gemini-cli-extension
  Run racket-sport tournaments from your AI assistant: fair draws, scores, live standings.
• com.adspirer/ads — last commit 2026-08-04, shares gemini-cli-extension
  Manage Google, Meta, Amazon, TikTok, LinkedIn & ChatGPT ads. 430 tools for campaigns & analytics.
• Final POS — last commit 2026-07-28, shares gemini-cli-extension
  Build custom POS, kiosk, self-checkout & in-person payment apps with AI agents on Final POS.
• InvoiceXML — last commit 2026-07-20, shares gemini-cli-extension
  Create, validate, convert & extract compliant e-invoices (UBL, Factur-X, ZUGFeRD, XRechnung)

These share tags the maintainers applied themselves, such as gemini-cli-extension. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

How the author describes it

Topics the maintainer set on GitHub: gemini-cli-extension.