explain — trident MCP Tool
explain
(explain) is one of 23 tools on the
trident
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explain from your client
- Claude Code trident explain run in your project directory
- Claude Desktop trident explain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor trident explain ~/.cursor/mcp.json
- VS Code trident explain .vscode/mcp.json
- Zed trident explain ~/.config/zed/settings.json
- Windsurf trident explain ~/.codeium/windsurf/mcp_config.json
- Cline trident explain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI trident explain ~/.gemini/settings.json
- Grok trident explain .mcp.json (in your project root)
- ChatGPT trident explain Settings → Connectors → Advanced → Developer mode
- Claude.ai trident explain Settings → Connectors → Add custom connector
- LangChain trident explain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http trident https://mcp.tridentchart.com/mcpOther tools on this server
- get_trident_spec
- get_generator_guide
- get_comprehensive_example
- validate_trident
- get_quick_start
- open_document
- get_document_summary
- get_recent_changes
- add_node
- update_node
- delete_node
- add_container
- update_container
- delete_container
- add_connection
- delete_connection
- get_document_png
- add_annotation
- update_annotation
- delete_annotation
- update_canvas_graphic
- make_suggestion
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.