Cursor MCP tools not showing
TL;DR
Cursor MCP tools may not appear because the server is not connected, the configuration is invalid, or Cursor failed to start the server. Verify the connection status, validate the config, and reload Cursor's MCP servers.
Diagnostic checks
Confirm the server shows as connected in Cursor's MCP view. If it does not, validate the config JSON and the transport. A remote server must be reachable; a local server must launch successfully.
Reload
Cursor lets you reload or reconnect servers. After editing configuration, reload the server list so Cursor re-reads the config and restarts the server.
In this collection
- Best MCP servers →
- How to choose an MCP server →
- Verified MCP servers →
- MCP server comparison methodology →
- MCP registries, directories, and marketplaces →
- MCP servers for databases →
- Read-only database access with MCP →
- MCP servers for developers →
- MCP browser automation →
- MCP servers for search and research →
- MCP servers for productivity →
- MCP servers for DevOps and cloud →
- Enterprise MCP →
- Postgres MCP server guide →
- Playwright MCP →
- MCP server not showing in Claude Desktop →
- MCP connection refused and timeout errors →
- Claude Desktop MCP configuration →
- VS Code MCP configuration →
- Remote MCP servers with OAuth →
- MCP server for GitHub →