MCP CLI
Everything you test in the app, from the terminal.
The MCPJam CLI runs the same checks as the app. Probe a server, step through an OAuth flow, call a tool, or run a conformance suite, then wire any of it into CI with pass/fail exit codes.
MCPJam CLI
Probe, debug, and test MCP servers from your terminal.
$ mcpjam docs
- [1]CLI Overview
- [2]MCPJam as an MCP Server
- [3]Server Inspection
- [4]OAuth Conformance
- [5]OAuth Login & Debugging
- [6]XAA Debugger (CLI)
- [7]MCP Apps Conformance
- [8]Tools, Resources & Prompts
- [9]CI / CD
- [10]CLI Telemetry
Select a section to open the docs →
Everything the app does, as commands
One-command health check
mcpjam server doctor runs a single probe across connectivity, auth, and tools, so you see what's broken before you dig into any one check.
OAuth conformance
mcpjam oauth conformance validates auth against any protocol version and registration method, the same coverage as the OAuth debugger, in one command.
Run tools and server checks
List and call tools with mcpjam tools call, and triage connectivity and capabilities with the mcpjam server commands.
Evals and conformance in CI
Run protocol, OAuth, and MCP Apps conformance headlessly with pass/fail exit codes you can gate a build on, plus hosted eval runs. (For an exit-code eval gate, run @mcpjam/sdk suites in your test runner.)
Probe, then run the exact checks you need
Start with a full health check, then drill into OAuth, tools, or evals.
# Install once
npm i -g @mcpjam/cli
# One-shot health check: connectivity, auth, and tools
mcpjam server doctor --url https://your-server.com/mcp
# OAuth conformance for a protocol version and registration method
mcpjam oauth conformance --url https://your-server.com/mcp \
--protocol-version 2025-11-25 --registration dcr
# Call a tool with JSON arguments
mcpjam tools call --url https://your-server.com/mcp \
--tool-name get_weather --tool-args @params.jsonFrequently asked questions
It runs the same checks as the app from your terminal: probe and debug servers, step through OAuth and run conformance suites, list and call tools, read resources and prompts, and run evals. See the CLI docs for every command.
A one-shot health check. It probes your server, connects, and sweeps its capabilities in a single command, so you get connectivity, auth, and tool status at once.
Yes. mcpjam oauth conformance validates auth across protocol versions and registration methods in one command, the same coverage as clicking through the OAuth debugger by hand.
Yes. Health-check and conformance commands run headlessly and return pass/fail exit codes to gate any build; run @mcpjam/sdk eval suites in your test runner for an exit-code eval gate. See the CI/CD actions page.
Bring MCP testing to your terminal.
Probe a server, run OAuth conformance, call tools, and run evals, then gate every build on the results.
Open source · npm i -g @mcpjam/cli