Short answer
Use MCP Inspector to explore a server, debug OAuth, and run quick CLI smoke and load checks. Use SineFrame M3 when you need pytest tests and proof that Claude Code, Codex or OpenCode actually call your tools. Many teams will want both: Inspector while building, M3 as the CI gate for agent behavior.
How do SineFrame M3 and MCP Inspector differ?
MCP Inspector, published by the Model Context Protocol project, ships one npm package with a web UI, a terminal UI, and a CLI. You connect a server over stdio, SSE, or Streamable HTTP, list and call its tools by hand, and walk through OAuth step by step. The CLI makes one request per call with JSON output and stable exit codes, and its smoke-testing guide pairs it with jq for assertions. It describes that guide as deliberately not a conformance suite.
M3 treats MCP testing as Python code. Tests are pytest tests that call the server directly, without a model, or run a real coding agent against it and assert on the tool calls the agent made. Runs are saved locally, compared against a baseline, and gated in CI with m3 ci test.
The pages Inspector publishes describe no way to run an LLM or coding agent against your server; a sampling request from the server is answered by a person in the terminal UI. That is the main gap M3 fills.
How do their capabilities compare?
Where one side does not describe a capability, the table says so. That is not a claim the capability is impossible.
| Capability | SineFrame M3 (v0.3.2) | MCP Inspector (2.15.0) |
|---|---|---|
| How tests are written | Python and pytest tests, run with m3 test | CLI calls with jq assertions in a shell script |
| Interactive debugging | Local viewer for saved runs and traces | Web UI, terminal UI, per-tool history and re-run |
| Transports | stdio and Streamable HTTP | stdio, SSE, and Streamable HTTP |
| Authentication | Headers, bearer secret references, environment credentials | Full OAuth client with step debugging and a stored-auth CI mode |
| Agent or LLM in the loop | Claude Code, Codex, OpenCode, Pi, and ACP agents | Not described |
| Assert on agent tool calls | to_have_tool_call on recorded evidence | Not applicable |
| Pinned agent versions | Managed runtime downloads and records exact versions | Not applicable |
| Schema and metadata lint | m3 lint: per-agent rules plus Claude, OpenAI, and Muse directory rules | --strict schema portability check |
| Load testing | Not described | --load with latency, error, and throughput gates |
| CI gate | m3 ci test; a run with no executed tests fails | Exit codes from the CLI smoke-test recipe |
| Results history | Local SQLite store, baselines, opt-in upload | Output files and load-test baselines |
| Install | uv tool install sf-m3-cli (Python 3.10+) | npx @modelcontextprotocol/inspector (Node 22.23.4+) |
| License | Apache-2.0 | Apache-2.0, MIT, and CC-BY-4.0 during a relicensing |
When is MCP Inspector the better fit?
Choose Inspector when you want to poke at a server by hand: list its tools, call one with chosen arguments, and read the raw response. It is also the stronger tool for authentication, with interactive OAuth, step-up prompts, a debug trace of each OAuth step, and a stored-auth mode that fails fast in CI instead of waiting for a browser.
Inspector also covers checks M3’s docs do not describe: load tests with latency and error-rate gates, MCP Apps probing, and skills verification. If your CI is Node-only and you want a model-free smoke test, its CLI fits without adding Python.
When is SineFrame M3 the better fit?
Choose M3 when the question is whether an agent uses your server. Agents skip servers often: in our runs across 21 servers, Codex skipped the server on 44.5% of the trials where it should have called it, and Claude Code on 36.5%. M3 runs those agents for real, at pinned versions, and an assertion on the recorded call fails even if the agent’s reply claims it used the tool.
M3 also fits teams that already write pytest: tests sit beside the rest of the suite, with fixtures, selection, parallel workers, saved runs, and baselines. m3 lint checks metadata against what specific Claude Code and Codex versions do, and against the Claude, OpenAI, and Muse directory rules.
Can you use MCP Inspector and SineFrame M3 together?
Yes. A common split is Inspector while building and debugging auth, and M3 for the regression gate on agent behavior. In CI the two run side by side: Inspector’s CLI smoke and load checks, and m3 ci test for pytest and agent tests. Running both linters is cheap, since --strict reports schema portability and m3 lint reports agent-specific and directory findings.
Frequently asked questions
- Can MCP Inspector test whether Claude Code or Codex calls my tool?
- Not according to its published docs, which describe calling tools directly from the web UI, terminal UI, or CLI. M3 runs the agents themselves and asserts on the tool calls they make.
- Can MCP Inspector run in CI?
- Yes, through its CLI: one request per call, JSON output, and stable exit codes, with jq for assertions. Its docs recommend pinning an exact Inspector version in CI.
- Are both free?
- Yes. Both are open source. M3 is Apache-2.0. Inspector is mid-relicensing, with new code under Apache-2.0, docs under CC-BY-4.0, and some older contributions under MIT.
Related
Try it on your own MCP server
SineFrame M3 is free and open source (Apache-2.0). Direct tests need no model or API key, and runs stay on your machine unless you publish them.