# wong2/mcp-cli [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/wong2/mcp-cli  
**GitHub Stars:** 447  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wong2-mcp-cli

## Description
A CLI inspector for the Model Context Protocol

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "mcp-cli": {
    "url": "http://localhost:8000/mcp"
  }
}
```

## Documentation

## What wong2/mcp-cli MCP server does

The wong2/mcp-cli MCP server is a command-line interface for examining and using MCP servers. It exposes the protocol primitives that a developer typically needs to inspect: tools, resources, and prompts. From the CLI, you can list those primitives, call tools, read resources, and retrieve prompts.

The tool is useful when you need to verify an MCP server independently of a full host application, investigate what a server exposes, or exercise one operation from a shell script. It can also act as a client for servers started locally or already running elsewhere.

## How it works

The wong2/mcp-cli MCP server accepts several ways to identify an MCP server:

- With no arguments, it reads the Claude Desktop configuration.
- With `-c`, it reads a supplied configuration file using the same format.
- With `npx`, it starts an npm-based server and passes command arguments through.
- With `node`, it starts a locally developed JavaScript server.
- With `--url`, it connects to a Streamable HTTP endpoint.
- With `--sse`, it connects to an SSE endpoint.

Interactive use lets you browse the available primitives. Non-interactive commands address a target using the form `<server-name>:<target>`, making direct invocation suitable for automation. Tool and prompt arguments can be supplied as JSON with `--args`.

## Setup and configuration

Run the CLI through `npx`:

```bash
npx @wong2/mcp-cli
```

To use a specific configuration file, provide its path:

```bash
npx @wong2/mcp-cli -c config.json
```

When launching an npm package or local server, add `--pass-env` if that process needs environment variables from the current shell. HTTP and SSE connections are configured by passing the relevant endpoint URL on the command line. Stored data, including OAuth tokens, can be removed with the `purge` command.

## Tools and capabilities

The wong2/mcp-cli MCP server supports these operations:

- List tools, resources, and prompts.
- Call a named tool, with optional JSON arguments.
- Read a named resource.
- Retrieve a prompt, with optional JSON arguments.
- Start MCP servers from npm packages or local Node.js files.
- Connect to Streamable HTTP and SSE servers.
- Use OAuth with SSE and Streamable HTTP servers.
- Run commands interactively or without prompts.

## Limitations and notes

The CLI is an inspector and client for MCP servers, not a directory of server implementations. Its configuration format follows Claude Desktop's format, and the README specifically documents use with Claude Desktop configuration. Environment variables are not declared by the CLI itself; `--pass-env` forwards variables from the invoking shell to a launched server when needed. The documented examples use Node.js-oriented commands and `npx`.

_Full upstream README: https://allmcps.com/mcp/wong2-mcp-cli/readme_