Fix
Cursor MCP Not Working / 'No Tools Found' — Fix
By The Field Academy Editorial TeamUpdated
An MCP server fails in Cursor usually because the start command or path is wrong, an API key/env var is missing, or there's a stdio-vs-remote mismatch. Test the exact command in a terminal, supply the required env vars, and confirm the server shows enabled tools after a reload.
Why does my Cursor MCP server show 'no tools found'?
- The command/path is wrong or the package isn't installed.
- Missing env vars / API keys, so the server crashes on start.
- stdio vs remote mismatch (a remote server needs a URL, not a command).
- The server started but exposes no tools, or too many tools are enabled across servers.
How do I fix an MCP server that won't connect?
- 1Run the exact start command in a terminal — confirm it launches.
- 2Add the required env vars / API keys to the MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. config.
- 3Match the transport: command for stdio, URL for remote.
- 4Reload Cursor and check the server shows enabled (green) tools.
- 5Trim to the tools you need so the agent isn't overwhelmed.
Frequently asked questions
Why won't my MCP server connect in Cursor?
Most often the start command fails — wrong path, missing dependency, or a missing API key. Run it in a terminal first, then re-check the env vars and transport (stdio vs remote).
How do I add an MCP server to Cursor?
Use Cursor Settings → MCP or a .cursor/mcp.json file with the server's command (stdio) or URL (remote) plus any env vars. See the MCP setup guide.
Sources & last verified
Cursor ships frequently. Facts verified against primary sources on June 15, 2026.