analyze_trace — Agent Trace Check MCP Tool
analyze_trace
(analyze trace) is one of 3 tools on the
Agent Trace Check
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_trace from your client
- Claude Code Agent Trace Check analyze_trace run in your project directory
- Claude Desktop Agent Trace Check analyze_trace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Trace Check analyze_trace ~/.cursor/mcp.json
- VS Code Agent Trace Check analyze_trace .vscode/mcp.json
- Zed Agent Trace Check analyze_trace ~/.config/zed/settings.json
- Windsurf Agent Trace Check analyze_trace ~/.codeium/windsurf/mcp_config.json
- Cline Agent Trace Check analyze_trace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Trace Check analyze_trace ~/.gemini/settings.json
- Grok Agent Trace Check analyze_trace .mcp.json (in your project root)
- ChatGPT Agent Trace Check analyze_trace Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Trace Check analyze_trace Settings → Connectors → Add custom connector
- LangChain Agent Trace Check analyze_trace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-trace https://agenttrace.openkrill.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 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.