mcp-servers-cli

# mcp-servers-cli Inspect, call and drive any MCP server from the command line. Point it at a local process, a remote HTTP endpoint, or an entry in a `claude_desktop_config.json`-style file, and it lists the tools, resources and prompts the server exposes — then lets you exercise them. ## Installation Run it without installing anything, with [uv](https://docs.astral.sh/uv/): ```bash uvx mcp-servers-cli inspect --stdio "uvx mcp-server-fetch" ``` Or install it once, with the Anthropic backend if you need it: ```bash uv tool install mcp-servers-cli uv tool install 'mcp-servers-cli[anthropic]' ``` From a clone, for development: ```bash uv sync --all-groups uv run mcp-servers-cli --help ``` ## Commands Every command takes exactly one target: `--stdio`, `--http` or `--config` with `--server`. ```bash # What does this server expose? mcp-servers-cli inspect --stdio "uv run server.py" mcp-servers-cli inspect --http https://example.com/mcp mcp-servers-cli inspect --config config.json --server fetch # Call one tool mcp-servers-cli call fetch '{"url": "https://example.com"}' --stdio "uvx mcp-server-fetch" # Read one resource mcp-servers-cli read "tasks://stats" --stdio "uv run server.py" # Inspect, then stay interactive mcp-servers-cli repl --stdio "uv run server.py" # Let a model use the tools to answer mcp-servers-cli agent "What is 2 + 3?" --model qwen3.5:4b --stdio "uv run server.py" ``` Inside the REPL: `call <tool> <json>`, `read <uri>`, `list`, `quit`. Tool results are printed as JSON from their structured content when the tool declares one, so a tool returning a list prints that list, not MCP's `{"result": ...}` wrapper. Resource contents and text results that hold JSON are printed as that JSON, other text as plain text. In a terminal, long JSON lines wrap; piped to a file or to `jq`, the JSON is written as is. `inspect` lists resource templates such as `report://{path}` apart from fixed resources. ## Agent `agent` hands the server's tools to a model…