Skip to content
MCPDev

Debug

When a client says nothing useful, take the client out of the loop. Connect to the server directly, look at the raw messages, and only then go back to the client’s configuration.

Start here

Section titled “Start here”
  1. Test a server with the MCP Inspector: call the server without any client.
  2. Checklist for a stdio server that will not start: stdout, environment, PATH and paths, in a fixed order.
  3. Where clients write MCP logs: find the server’s own error output.

If you already have an error message, search the error catalog for its exact text.

MCPDev is community documentation. It is not affiliated with the Model Context Protocol project or with the vendors of the clients it covers.