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