mcp-explorer CLI
Command-line inspector for HTTP MCP servers: lists tools, schemas, prompts and resources and calls any tool by hand.
- 134 ★ on the repository
- Last commit
Extended access
Why this level
- `call` really executes server tools, including ones that change data.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/mcp-explorerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- `call` really executes server tools, including ones that change data.
This is third-party code. Review the repository files before installing.
What it does
mcp-explorer is a Python command-line tool that connects to an MCP server by URL and shows what it can do. `list` prints tools compactly, `inspect` expands one tool with full input and output schemas, and `prompts` and `resources` enumerate prompts and resources across every page of results. `call` invokes a tool: arguments come as a JSON object or repeated `-a` options, values are coerced by the tool schema and validated before sending. `info` reports protocol version and server capabilities, and `doctor` checks compatibility with both the new sessionless protocol and the legacy handshake. The `--json` and `--stateless`/`--legacy` options work after any command.
Who it is for. MCP server authors debugging tools without a client, and developers who want to see a third-party server definitions before wiring it to an agent.
Good fit when
- You need a quick list of a third-party HTTP server tools before connecting it to Claude Code.
- Your own server behaves oddly for an agent, so you replay a tool call by hand with the same arguments.
- Before a server release you confirm it answers on both the new sessionless protocol and the legacy one.
- CI needs JSON tool definitions to diff schemas between server versions.
Not a fit when
- The server runs locally over stdio: every README example uses a URL.
- You want a graphical interface with call history: the tool is command-line only.
- A tool changes production data and a trial run is unwanted: `call` really executes it.
Example request
List the tools of the MCP server at https://example.com/mcp and describe the argument schema of the `execute_sql` tool.Limitations
The tool works with servers reachable by URL; README examples show only streamable HTTP. MCP 2 without sessions is the default, and the legacy handshake needs `--legacy`, so an older server may reject the first request. `call` really executes the tool and can change data on the server. Passing tokens or authorization headers is not described in the README, so access to protected servers is unconfirmed. The project is small and maintained by one author.
How to disable. Remove the package with `pip uninstall mcp-explorer`. The tool does not change servers or their data until `call` is run.
FAQ
How do I check that a server is compatible?
Run `mcp-explorer doctor URL`. It checks both the sessionless mode and the legacy handshake mode, and the exit code follows the selected mode.
How do I pass arguments to a tool?
Give a JSON object as the third parameter or repeat `-a NAME VALUE`. When both are used, individual `-a` options override matching JSON keys.
How do I see the full description of one tool?
Run `mcp-explorer inspect URL TOOL`. With `--json` the output arrives as one object with annotations and schemas.
Does it work with older servers?
Yes, `--legacy` switches to the legacy handshake. Without it the tool uses sessionless MCP 2.
Can arguments be read from a file?
Yes. Pass `-` instead of JSON and redirect the file to standard input: `mcp-explorer call URL TOOL - < arguments.json`.
Discussion
No questions or reviews yet.
Related
CLI toolsA command-line debugger for MCP servers from Giant Swarm: a REPL for tools, OAuth 2.1 and an MCP server mode for Cursor
A transparent proxy between an AI client and an MCP server: shows every JSON-RPC frame in the terminal, checks a capture in CI and exports spans
A local tool to test and debug MCP servers: chat with tools, inspect calls and run evals across clients
A lightweight CLI to discover, inspect and call MCP server tools straight from the shell
Checks a McDonald's China MCP connection: tool count and names, auth failure responses and why prices come back as zero.
An MCP server that lets an agent read files, search code and run commands in a workspace
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| mcp-explorer (this card) | no | 134 | |
| MCP Inspector | no | 11,243 | a graphical MCP inspector; mcp-explorer works through terminal commands and emits JSON for scripts |
| MCPJam Inspector | no | 2,302 | an MCP testing environment with an interface; mcp-explorer stays a small command-line tool |
README in short
The README covers each command with examples and `--help` output, and the shared `--json` and `--stateless`/`--legacy` options apply after any command.