What this error means
tools/list failed (MCP error -32601: Method not found); retrying once is a Claude Code failure pattern reported for developers trying to fix claude code mcp -32601 error causing slow cold start in vscode extension. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
VSCode extension v2.1.142: claude-vscode IDE-bridge MCP server fails tools/list with -32601 on every session. Client retries once, fails, logs error event. Adds ~50s to cold start on slow hosts. Category mapped to AI Coding Tools (Claude Code).
Common causes
- VSCode extension v2.1.142: claude-vscode IDE-bridge MCP server fails tools/list with -32601 on every session. Client retries once, fails, logs error event. Adds ~50s to cold start on slow hosts. Category mapped to AI Coding Tools (Claude Code).
Quick fixes
- Confirm the exact error signature matches
tools/list failed (MCP error -32601: Method not found); retrying once. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.