Learn · Track
One page per error message. Each says what the message means according to the specification or the runtime, which side causes it, how to confirm the cause, and how to fix it. Start from the exact text you see: connection closed, ENOENT, session not found, method not found, invalid params, invalid_client, insufficient_scope, timeouts, missing tools and agents that loop.
Why an MCP client reports -32000 Connection closed: the stdio server exited, never started or broke its stdout channel. How to find the cause and fix it.
The MCP client could not find npx, uvx or node on the PATH it launches servers with. Why it works in your terminal but not in the app, and how to fix it.
Why a local MCP server reports a missing token: the variable was never passed, the client builds a short environment, or a placeholder was not expanded.
The MCP server starts and connects, yet the agent sees no tools. Check the tools capability, listing errors, pagination, filters, policies and names.
A Streamable HTTP MCP server answered 404 for an Mcp-Session-Id it no longer knows. Why it happens after restarts and scale-out, and how a client recovers.
Why MCP tool calls time out, what -32001 does and does not mean, how cancellation and progress work, and when a retry is safe or could act twice.
What happens when an MCP client and server speak different protocol revisions: the -32020 to -32022 errors of 2026-07-28, older 400 answers, and fixes.
Why an MCP server or client answers -32601 Method not found: a typo, a capability it never offered or a revision mismatch, and how to check.
What MCP error -32602 means, why models send tool arguments a JSON Schema rejects or call a tool that does not exist, and how to make calls validate.
Why an MCP tool response exceeds the allowed tokens or fills the context window, and how to fix it on the server, in the client and in the agent.
Why the reference filesystem MCP server refuses a path: allowed directories, roots from the client, relative paths, symlinks and containers. Safe fixes.
Why connecting a remote MCP server fails with invalid_client: a stale registered client id, no dynamic registration, a redirect URI mismatch or wrong auth.
The MCP client could not discover where to sign in. How OAuth metadata is found, and the path, issuer, redirect and TLS problems that break it.
A remote MCP server accepted your token but refused a tool with 403 insufficient_scope. How to read the challenge and fix it with step-up authorization.
The model answers in text instead of calling a tool. Check what was sent, tool support, tool choice, descriptions, tool count and the prompt, in order.
Why an agent repeats one tool call until it hits max iterations: errors it cannot act on, results it cannot use, no stop rule. How to break the loop.
Prerequisites: none, though the pages assume you know what an MCP server is. MCP transports and MCP authorization explain the mechanisms most of these errors come from.
Not here? Common issues covers problems with L2M itself: setup, webhooks, templates and parsers. To start from a working agent instead, import one from the recipes.
This website (not the L2M product) uses Google Analytics, only after you accept cookies. Cookie settings