MCP server not working in Cursor or VS Code?
Check config root key first. VS Code expects 'servers' while most other clients use 'mcpServers'. A valid JSON file with the wrong key is silently ignored.
Open IDE endpoint troubleshootingRun live probe checks for handshake, tool discovery, schema availability, and protocol metadata. This playground is designed for real debugging, not just a status ping.
Configure endpoint and auth secret, then run probe.
No active probe session
Add endpoint details in Control Panel and run probe to inspect handshake, tools, and server metadata.
These are high-frequency issues from real support logs and ranking queries around "MCP server not working". Fix these before deep debugging.
Check config root key first. VS Code expects 'servers' while most other clients use 'mcpServers'. A valid JSON file with the wrong key is silently ignored.
Open IDE endpoint troubleshootingYour server can pass handshake but still return tool_count = 0. Verify your list tools handler and make sure tool schemas are valid JSON and not empty.
Open method mismatch troubleshootingFor local stdio servers this is often stdout contamination or PATH mismatch. Move logs to stderr and use absolute runtime paths (node/python) in the server command.
Open connection closed troubleshootingMost failures are transport or auth mismatch. Confirm your endpoint transport (HTTP vs SSE), headers, and token format exactly match what your server expects.
Check team policy restrictionsNeed full deep-dive with exact fixes?Read the complete troubleshooting guide