MCP Inspector in CI/CD
Inspector is primarily an interactive development client. For CI, favor SDK-driven tests and use Inspector/CLI automation only as a smoke-test layer when your chosen Inspector version exposes stable automation commands.
Good CI checks
- Server process starts successfully.
- HTTP health/reachability works.
- Capability discovery succeeds.
- Expected tool names and schemas exist.
- One or two critical calls return correct structure.
Why not make Inspector your whole test suite?
Your domain logic, authorization, and edge cases are easier to express and maintain in pytest or your language's test framework. Inspector is a useful external client perspective, not a replacement for application tests.
Inspector V2 is under active development in 2026. Pin versions in CI and avoid depending on undocumented output formats.