MCP Inspector
Inspect MCP server tools, resources and connection behavior interactively.
Browse category →Workflow problem
Debug MCP servers in Claude Code
An MCP server can register but fail to expose tools, connect, or return the expected result.
The problem
An MCP server can register but fail to expose tools, connect, or return the expected result.
Native approach
Use `claude mcp list` to check configured servers and `/mcp` inside Claude Code to inspect connection status. Inspect server stderr and configuration when a connection fails.
Official Claude Code documentation ↗Tools to consider
Start with a protocol inspector, which connects to the server directly, before blaming agent prompts. The MCPJam Inspector catalog entry documents Cursor support, not Claude Code integration. Traffic viewers help when calls reach the server but results surprise you.
MCPJam Inspector
Trace and evaluate MCP server interactions in a visual workbench.
Browse category →claude-tap
Inspect coding-agent API traffic in a local trace viewer.
Browse category →FAQ
Why are my MCP tools missing?
Check server startup, configuration scope and connection status first.
Will an inspector fix the server?
No. It helps reproduce and observe protocol behavior.