MCP error -32000: Connection closed. Why MCP servers exit on startup

MCP error -32000: Connection closed means the server process your client started is gone. We launched 171 local (stdio) MCP servers with no credentials; 34 of 171 failed to start or answer the handshake (31 exited, 2 failed to install, 1 timed out). Below is what each one printed, grouped by cause.

Last tested 2026-10-22

How we test: methodology. Context cost: lowest context cost MCP servers. Not tested by us: security, output quality, and behaviour with real credentials.

Check these first

1. Run the command yourself. Copy command and args from your config into a terminal. If it prints an error and returns to the prompt, that error is the cause.
2. Set required environment variables in the server's env block. Many servers exit at once without a key or URL.
3. Check the start command. Some packages need a subcommand or argument; some have no runnable entry point at all (see below).

Causes we recorded, with verbatim output

Our stored output keeps the end of each server's stderr. Excerpts are verbatim, shortened to one line. Our client is not Claude Code, Claude Desktop or Cursor; we have not tested the suggested fixes.

mcp Python SDK 2.x API change (8)

The package was written for version 1 of the mcp Python SDK and crashed on import under 2.x. What to try not tested by us: See the mcp Python SDK 2.x page for the verbatim errors and the mcp<2 pin (not tested by us).

Install failed (2)

The package did not install, so there was no process to start. What to try not tested by us: Read the install error first: a native build step (node-gyp) needs build tools; a package whose versions were all yanked cannot be installed at all.

No runnable entry point (3)

The package installed but declares no executable (no npm bin entry, no Python console script), so npx/uvx had nothing to run. What to try not tested by us: Check the package README for the real start command or the right package name; npx can be pointed at a named binary with npx -y --package=<pkg> <bin>.

Needs a command-line argument or subcommand (6)

The server printed a usage error and exited because it was started with no arguments. What to try not tested by us: Add the argument or subcommand its README names (for example a --tools list, a database path, or a run/mcp subcommand) to args in your MCP config.

Needs a running service, file or program (5)

The server tried to reach something that was not there on our test machine (a local database or Docker socket, a config or OAuth keys file, a URL setting, or another program on PATH) and exited. What to try not tested by us: Start the service or create the file it names before the client launches the server, and put any URL or path it needs into env or args.

Package retired in favour of another install (1)

The npm package itself printed that it is deprecated and pointed to a different install. What to try not tested by us: Follow the install it names (here, the vendor CLI's built-in MCP command).

Python dependency missing or incompatible (2)

Import failed inside a dependency: a module the package uses was not installed, or an installed version did not match. What to try not tested by us: Install the missing module or pin the dependency version the package was built against; reinstalling into a fresh environment rules out leftovers.

Tried to install its own dependencies at startup (1)

The npm package ran pip at startup to install Python requirements; pip refused (PEP 668, externally managed Python), and the server exited. What to try not tested by us: Install the requirements file it names into a virtual environment yourself, or run the server from an environment where pip installs are allowed.

Started an HTTP server instead of stdio (1)

The process came up as an HTTP server (it printed a localhost URL) and never answered on stdin/stdout, so our stdio client timed out. What to try not tested by us: Either connect your client to the URL it prints, or start it in stdio mode if its README offers one.

Node.js crash on startup (3)

Node printed an uncaught-exception stack trace and exited. Our stored log keeps only the end of stderr, so the first error line was cut. What to try not tested by us: Run the exact command from your config in a terminal and read the first error line.

Exited with no output (2)

The process exited with code 1 and printed nothing on stdout or stderr. What to try not tested by us: Run the exact command from your config in a terminal; check the README for required environment variables or arguments.

Servers that started cleanly: 137 of 171 stdio servers completed the handshake or answered with a credential check. Browse working ones: all rankings · best free MCP servers.

FAQ

What does MCP error -32000: Connection closed mean?

In the official MCP TypeScript SDK, -32000 is the ConnectionClosed error code. For a local (stdio) server it means the server process your client started went away before or during the handshake. The client message does not say why; the server's own output does.

Why does an MCP server close the connection right after it starts?

In our tests through 2026-10-22, of the local (stdio) MCP servers we launched, 34 of 171 failed to start or answer the handshake (31 exited, 2 failed to install, 1 timed out). By cause, with counts: mcp Python SDK 2.x API change (8); Install failed (2); No runnable entry point (3); Needs a command-line argument or subcommand (6); Needs a running service, file or program (5); Package retired in favour of another install (1); Python dependency missing or incompatible (2); Tried to install its own dependencies at startup (1); Started an HTTP server instead of stdio (1); Node.js crash on startup (3); Exited with no output (2). A further 29 stopped at a credential check without an API key or token.

How do I find the real error behind -32000?

Run the exact command and args from your MCP config in a terminal and read what it prints, or open your client's MCP server log. A working stdio server prints nothing on stdout and waits for input.

Did you reproduce -32000 in Claude Code, Claude Desktop or Cursor?

No. We launched each server with our own stdio MCP client and recorded what the process printed when it exited. We did not run these servers inside those clients, and we have not tested the suggested fixes.