Cursor says 'no tools or prompts' for your MCP server — fix it
Symptom: In Cursor's MCP settings the server is listed but greyed/red with 'no tools or prompts available', so nothing is usable.
Short answer
'No tools or prompts' means Cursor connected to the server but the server advertised zero tools. That's different from a connection failure. The usual reasons: the server needs an API key it didn't get, it needs a specific sub-command/flag to run in server mode, or Cursor cached an old failed state and just needs a reload (or toggle off/on).
Why it happens, ranked by how often it's the real cause
1. Missing credentials — the server starts but exposes nothing
Some servers only register tools after authenticating; without the key they connect but list nothing.
Fix: Add the required API key/token to the server's env in your mcp.json, then reload.
2. The server needs an explicit 'serve'/'mcp' sub-command
A few packages are CLIs that only speak MCP when launched with a specific argument; without it they start in the wrong mode.
Fix: Check the server's page here for the exact args — some need e.g. `... mcp --stdio` rather than the bare command.
3. Cursor cached a stale/failed state
Cursor sometimes holds onto a previous failed handshake even after you fix the config.
Fix: Toggle the server off and on in Settings → MCP, or fully restart Cursor.
Fix it step by step
- 1Open Cursor Settings → MCP and check the dot: red = not connecting (different problem), grey with 'no tools' = connected-but-empty.
- 2Add any required env keys to the server's entry in mcp.json.
- 3Confirm the args match the server's documented MCP launch command.
- 4Toggle the server off/on, or restart Cursor, to clear cached state.
Still stuck?
If it still lists no tools, run the server's command in a terminal and watch what it prints — a server that exposes tools will respond to an MCP `tools/list` call. If it doesn't, the issue is the server/config, not Cursor.
FAQ
Why does Cursor say 'no tools or prompts' for my MCP server?
Cursor connected, but the server advertised no tools. Most often it needs an API key it didn't get, needs a specific sub-command to run in MCP mode, or Cursor is holding a stale state — toggle it off/on.
What's the difference between a red dot and 'no tools' in Cursor MCP?
A red dot means the server failed to connect (a startup/command problem). 'No tools or prompts' means it connected fine but exposed nothing — usually credentials or a wrong launch mode.