Claude Code / AI Coding Tools

Claude Code MCP Server Crashes With -32000 Generic Error

Developer configures an MCP server for Claude Code but it immediately fails with -32000; needs systematic troubleshooting steps (command isolation, env vars, stdout pollution, Node.js event loop). Includes evidence for Claude Code troubleshooting demand.

Category
AI Coding Tools
Error signature
Connection closed / MCP server <name>: error -32000 — generic JSON-RPC server error indicating MCP subprocess crashed during init
Quick fix
Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated

What this error means

Connection closed / MCP server <name>: error -32000 — generic JSON-RPC server error indicating MCP subprocess crashed during init is a Claude Code failure pattern reported for developers trying to developer configures an mcp server for claude code but it immediately fails with -32000; needs systematic troubleshooting steps (command isolation, env vars, stdout pollution, node.js event loop).. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

codersera.com details -32000 as the JSON-RPC generic server-error code caused by MCP server process failing to start. Verified by GitHub issue GitNexus #1683: ‘MCP error with Claude: Failed to reconnect to gitnexus: -32000’. Root causes include missing binary, wrong Node version, missing env var, console.log() polluting stdio transport. Not covered in dev-error-db’s covered-errors.md.

Common causes

Quick fixes

  1. Confirm the exact error signature matches Connection closed / MCP server <name>: error -32000 — generic JSON-RPC server error indicating MCP subprocess crashed during init.
  2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
  3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

Sources checked

Evidence note: codersera.com details -32000 as the JSON-RPC generic server-error code caused by MCP server process failing to start. Verified by GitHub issue GitNexus #1683: ‘MCP error with Claude: Failed to reconnect to gitnexus: -32000’. Root causes include missing binary, wrong Node version, missing env var, console.log() polluting stdio transport. Not covered in dev-error-db’s covered-errors.md.

FAQ

What should I check first?

Start with the exact Connection closed / MCP server <name>: error -32000 — generic JSON-RPC server error indicating MCP subprocess crashed during init text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Connection closed / MCP server <name>: error -32000 — generic JSON-RPC server error indicating MCP subprocess crashed during init.