Trident MCP Server

by alexeibespalov Your server? Claim it

answering

Trident is answering right now. Last checked moments ago. 42 installs a week from npm. It exposes 23 tools. Last commit 6 Sep 2026.

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

Installs per day peak 26 · avg 7 · +27% w/w

a month agotoday

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

133 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 September 2026. No other catalogue keeps this.

6 Sep 2 tools changed the parameters they ask for add_node, update_node

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

File ships in the package but is absent from the source [пакет] index.js:1

этот файл ставится пользователю, но в репозитории его нет

Page executes code built at runtime demo.html:358

document.getElementById('markup-view').innerHTML = highlight(MARKUP);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add trident --transport http https://mcp.tridentchart.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "trident": {
      "url": "https://mcp.tridentchart.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.trident]
url = "https://mcp.tridentchart.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "trident": {
      "url": "https://mcp.tridentchart.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "trident": {
      "url": "https://mcp.tridentchart.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: TRIDENT_API_KEY (Optional Trident API key for document editing tools. Spec tools work without a key.). The author declared them in the registry entry; get the values from the project itself.

Available tools 23

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

annotation

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, section labels, or TODO markers. Appears immediately for all collaborators. 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_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.

container

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.

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

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.

node

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 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.

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.

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.

connection

add_connection

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.

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.

document

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.

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 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.

canvas

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 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.

comprehensive

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.

explain

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 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.

generator

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.

make

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:" 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.

open

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 — 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.

quick

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.

recent

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.

trident

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.

validate

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.tridentchart.com/mcp	streamable-http	answering	125 ms	0 min ago

Alternatives to Trident

same job, measured the same way

Flowzap

by flowzap-xyz

Create workflow, sequence, architecture, and mind map diagrams via AI assistants.

85 installs/wk local only

Agent-Native Design

by builderio

Agent-Native design tool - create and edit visual designs with agent assistance

answering

Composer

by olivergrabner

Give your AI coding agent an architecture canvas to design and evolve diagrams.

46 installs/wk local only

Knowtis

by knowtis

Create, search and manage Knowtis collaborative notes from AI assistants.

answering

Excalidraw Architect

by bv-venky

Generate beautiful Excalidraw architecture diagrams with auto-layout and component styling

578 installs/wk local only

Datadef

by datadef

Generate, edit, and export data-architecture diagrams from your AI. Column lineage, PNG in chat.

36 tools answering

Miro

by mcparmory

Create and manage collaborative boards, items, and diagrams programmatically

246 installs/wk local only

Drawarch

by ajey95

Create editable Draw.io architecture diagrams from prompts and reference images.

59 installs/wk local only

Trident — questions

Answers built from our own checks of this server.

What can Trident do?

It exposes 23 tools, read directly from the server on our last check. Among them: add_annotation, add_connection, add_container, add_node, delete_annotation, delete_connection and 17 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Trident mostly used for?

Its tools cluster around node, annotation and container. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Trident working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 133 ms. The bar chart above shows every period we have measured.

How do I connect Trident?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Trident need an API key?

No. Trident completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 23 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Trident?

It answers our handshake in 133 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Trident?

The npm package trident-mcp was installed 42 times in the last week. Week over week that is +27%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Trident open source?

We cannot say either way: written in JavaScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.