Why is my MCP server showing a red dot in Cursor?

A red dot means the server process failed to start. The usual causes are invalid JSON in mcp.json, a command that is not on your PATH, or an outdated Node version.

Why does my MCP server not appear in Cursor at all?

Either mcp.json is in the wrong place (it must be ~/.cursor/mcp.json or .cursor/mcp.json), or the JSON is malformed so Cursor cannot parse it. Reload the window after fixing.

How do I see MCP error logs in Cursor?

Open the MCP section of Cursor Settings; failed servers show an error, and the Output panel (MCP channel) has more detail.

Does npx need to be installed for MCP servers to work?

npx ships with Node.js. If npx is not found, install Node and make sure it is on your PATH, then reload Cursor.

MCP Server Not Showing Up in Cursor? How to Fix It

If an MCP server will not appear or shows a red dot in Cursor, check these five things in order: valid JSON in mcp.json, the server is toggled on in Settings → MCP, the command (usually npx) is on your PATH, Node is recent enough, and reload the Cursor window. One of these fixes it almost every time.

A red dot or a missing MCP server in Cursor almost always traces to one of five causes. Work down this checklist and it will connect.