Connect Trident and your agent gets 23 tools, among them add_annotation, add_connection, add_container. It answers at https://mcp.tridentchart.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 21 October 2026, succeeded.
Create and edit collaborative architecture diagrams with any AI assistant using the Trident 2D DSL.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: token, agentId, userName, annotation, action_explanation |
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. Inputs: token, agentId, userName, connection, action_explanation |
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. Inputs: token, agentId, userName, container, action_explanation |
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 positi Inputs: token, agentId, userName, node, action_explanation |
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. Inputs: token, agentId, userName, annotationId, action_explanation |
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. Requi Inputs: token, agentId, userName, connectionId, source, target |
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 Inputs: token, agentId, userName, containerId, deleteNodes, action_explanation |
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. Req Inputs: token, agentId, userName, nodeId, action_explanation |
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 othe Inputs: token, agentId, userName, explanation, entityId |
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 annotatio |
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 cor Inputs: token |
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 Inputs: 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 gene |
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 | 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 Inputs: token, since, limit |
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 | 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 Inputs: token, agentId, userName, suggestion, entityId |
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 Inputs: token, agentId, userName |
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. Inputs: token, agentId, userName, annotationId, changes, action_explanation |
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, Inputs: token, agentId, userName, canvasGraphicId, changes, action_explanation |
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. Inputs: token, agentId, userName, containerId, changes, action_explanation |
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. Inputs: token, agentId, userName, nodeId, changes, action_explanation |
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. Inputs: diagram |
Every block below points at https://mcp.tridentchart.com/mcp. Pick your client and copy.
claude mcp add --transport http trident https://mcp.tridentchart.com/mcp
{
"mcpServers": {
"trident": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.tridentchart.com/mcp"]
}
}
}{
"mcpServers": {
"trident": {
"url": "https://mcp.tridentchart.com/mcp"
}
}
}{
"servers": {
"trident": {
"type": "http",
"url": "https://mcp.tridentchart.com/mcp"
}
}
}{
"context_servers": {
"trident": {
"url": "https://mcp.tridentchart.com/mcp"
}
}
}{
"mcpServers": {
"trident": {
"serverUrl": "https://mcp.tridentchart.com/mcp"
}
}
}{
"mcpServers": {
"trident": {
"url": "https://mcp.tridentchart.com/mcp"
}
}
}name: Trident
version: 0.0.1
schema: v1
mcpServers:
- name: Trident
type: streamable-http
url: https://mcp.tridentchart.com/mcp{
"mcpServers": {
"trident": {
"httpUrl": "https://mcp.tridentchart.com/mcp"
}
}
}{
"mcpServers": {
"trident": {
"type": "http",
"url": "https://mcp.tridentchart.com/mcp"
}
}
}{
"mcpServers": {
"trident": {
"url": "https://mcp.tridentchart.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.tridentchart.com%2Fmcp&type=streamable_http&id=trident&name=Trident
It answered our last check on 21 October 2026 in 170 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
23, as returned by the server's own tools/list on 13 September 2026: add_annotation, add_connection, add_container, add_node, delete_annotation, delete_connection, delete_container, delete_node, and 15 more.
It answered our last check on 21 October 2026 in 170 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.tridentchart.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.alexeibespalov. Endpoint host: mcp.tridentchart.com. ARD identifier: urn:air:io.github.alexeibespalov:mcp:trident.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.