BuildStateTwin — EchoLedger MCP Tool
BuildStateTwin
(build state twin) is one of 11 tools on the
EchoLedger
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call BuildStateTwin from your client
- Claude Code EchoLedger BuildStateTwin run in your project directory
- Claude Desktop EchoLedger BuildStateTwin ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EchoLedger BuildStateTwin ~/.cursor/mcp.json
- VS Code EchoLedger BuildStateTwin .vscode/mcp.json
- Zed EchoLedger BuildStateTwin ~/.config/zed/settings.json
- Windsurf EchoLedger BuildStateTwin ~/.codeium/windsurf/mcp_config.json
- Cline EchoLedger BuildStateTwin ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EchoLedger BuildStateTwin ~/.gemini/settings.json
- Grok EchoLedger BuildStateTwin .mcp.json (in your project root)
- ChatGPT EchoLedger BuildStateTwin Settings → Connectors → Advanced → Developer mode
- Claude.ai EchoLedger BuildStateTwin Settings → Connectors → Add custom connector
- LangChain EchoLedger BuildStateTwin pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http echoledger-mcp https://mcp.echoledger.ai/mcpOther tools on this server
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.