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