Serverdex error reference · read 21 November 2026

Tools limited to 40 total (Cursor): what it means and how to fix it

Tools limited to 40 total · Too many MCP tools are enabled for this model

Cursor caps the number of MCP tools it sends to the model. When the enabled servers expose more tools than the cap, the extra tools are dropped and the panel shows this message. It is a client limit, not a server error.

Shown by: Cursor

Causes, most likely first — and the fix for each

  1. 1Too many servers enabled at once, or one server with a very large tool list (the median listed server has about 14 tools; the heaviest expose hundreds — see the Serverdex context-tax report).

    Fix: Disable the servers you are not using in the MCP panel, or disable individual tools per server where the client allows it; prefer servers with focused tool lists for the task at hand.

Still failing?

Work through the twelve general causes in order in MCP server not working: the causes, in order, check the exact config file path and shape for your client in the client setup guides, or generate a known-good config with the config generator.

Sources (read 21 November 2026)

Other MCP errors: MCP error -32000: Connection closed · MCP error -32001: Request timed out · MCP error -32601: Method not found · MCP error -32602: Invalid params · MCP error -32603: Internal error · MCP error -32600: Invalid request · HTTP 406 Not Acceptable from an MCP server · spawn npx ENOENT · spawn uvx ENOENT (and uv, docker) · Server transport closed unexpectedly · Client closed (Cursor) · No tools, prompts, or resources (Cursor) · Unexpected token … is not valid JSON · SSE error: Invalid content type, expected text/event-stream · Could not attach to MCP server (Claude Desktop) · Failed to reconnect to an MCP server (Claude Code) · MCP server needs authentication (401 Unauthorized) · MCP OAuth loop (infinite sign-in tabs) · executable file not found in $PATH (Antigravity) · MODULE_NOT_FOUND / No module named mcp.server.fastmcp.