inspector
MCP Inspector is the official developer tool for inspecting Model Context Protocol servers. It ships as a single package with three interfaces: a web UI for exploring a server interactively, a scriptable CLI for automation, CI and fast feedback loops for coding agents, and a terminal UI. You can connect to a server, list and call its tools, read resources, try prompts and see the raw protocol traffic.
It is essential for anyone building or debugging an MCP server: checking that tool schemas and descriptions look right, reproducing a bug a client reports, testing OAuth flows, or running automated checks in CI before releasing a server. The current v2 line reorganises configuration (separating `--config` and `--catalog`) and requires a newer Node.js; a migration guide covers the changes from v1.
Getting started: run `npx @modelcontextprotocol/inspector` for the web UI, or add `--cli` or `--tui` for the other interfaces. The Python SDK's `mcp dev` command also opens your server in the Inspector.
Features
Why choose it
Trade-offs
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!