What problem does it solve?
It helps you rapidly debug why a Model Context Protocol (MCP) server won’t connect or can’t successfully initialize and execute tool calls, reducing time lost to guesswork.
Core Features & Use Cases
- Inspector-based verification: Use the official MCP Inspector to confirm transport behavior (stdio, SSE, HTTP) and to inspect initialization, auth, tools/resources/prompts, and schemas.
- Targeted CLI smoke tests: Reproduce failures by running scripted tool calls like tools/list and the smallest failing tools to validate the exact failure point.
- Auth-safe debugging: Pass required headers (e.g., bearer tokens) without committing secrets by using your Doppler-run environment.
Quick Start
Use the MCP Inspector to verify the server can respond to tools/list, then reproduce the failing tool call with the same transport and exact auth headers.