analyze_trace — agent loop detector MCP Tool
analyze_trace
(analyze trace) is one of 3 tools on the
agent loop detector
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 loop detector analyze_trace run in your project directory
- Claude Desktop agent loop detector analyze_trace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent loop detector analyze_trace ~/.cursor/mcp.json
- VS Code agent loop detector analyze_trace .vscode/mcp.json
- Zed agent loop detector analyze_trace ~/.config/zed/settings.json
- Windsurf agent loop detector analyze_trace ~/.codeium/windsurf/mcp_config.json
- Cline agent loop detector analyze_trace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent loop detector analyze_trace ~/.gemini/settings.json
- Grok agent loop detector analyze_trace .mcp.json (in your project root)
- ChatGPT agent loop detector analyze_trace Settings → Connectors → Advanced → Developer mode
- Claude.ai agent loop detector analyze_trace Settings → Connectors → Add custom connector
- LangChain agent loop detector analyze_trace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-loop-detector https://api.lazy-mac.com/agent-loop-detector/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.