inspector

Why we included this project

Anyone building or maintaining a Model Context Protocol server will probably end up here, since this is the closest thing to a standard way to verify how your implementation actually behaves from a client's point of view. Point it at a server and you can list the tools it exposes, fire off live requests, and watch the responses or errors come back, which is exactly what you need when tracking down a contract mismatch. The same package ships a browser UI, a scriptable CLI for CI checks, and an interactive terminal mode, so you can switch tools without leaving your workflow. OAuth and client configuration are handled internally, which removes a good chunk of the setup friction when a server requires authorization before it will talk to you. Teams wiring MCP servers into agents will find these mismatches before shipping rather than after.