What this error means
Failed to create shell snapshot — Claude Code hangs when calling MCP servers is a Claude Code failure pattern reported for developers trying to fix claude code hanging when using mcp tool calls. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
GitHub Issue #58209 (open): Claude Code hangs during MCP server calls on Windows. Root cause: shell snapshot creation fails with git/bash path resolution error. Feedback ID da9a7874-6e1d-4044-937d-8b4b73c374. Platform: win32, Version: 2.1.139
Common causes
- Claude Code users relying on MCP servers experience complete hangs during tool invocation, blocking development workflows
- GitHub Issue #58209 (open): Claude Code hangs during MCP server calls on Windows. Root cause: shell snapshot creation fails with git/bash path resolution error. Feedback ID da9a7874-6e1d-4044-937d-8b4b73c374. Platform: win32, Version: 2.1.139
Quick fixes
- Confirm the exact error signature matches
Failed to create shell snapshot — Claude Code hangs when calling MCP servers. - 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.