MCP CLI client
A CLI to run LLM prompts and act as an MCP client from the terminal, with any MCP server and any model provider
- 675 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs connected MCP servers and their tools
- Keeps an LLM provider key in a local config
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/mcp-cli-clientDetects 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.
- Runs connected MCP servers and their tools
- Keeps an LLM provider key in a local config
This is third-party code. Review the repository files before installing.
What it does
MCP CLI client is a simple command-line program that runs an LLM prompt and acts as an MCP client. From the terminal you can connect any MCP-compatible servers, so the tool serves as an alternative to Claude Desktop. The model is set in ~/.llm/config.json: provider, model name, key and, if needed, a custom base_url for OpenRouter or a local model. The same file lists MCP servers with their launch command, args, environment variables and the tools that require confirmation or are excluded.
Who it is for. For developers who want a terminal MCP client with any LLM provider.
Good fit when
- You need to call MCP servers straight from the terminal
- You want an MCP client with a provider like OpenAI, Groq or a local model
- You need an alternative to a desktop client for scripts
Not a fit when
- You want a graphical client with a UI
- You are not ready to set up a config and a provider key
Example request
Run this prompt in the terminal using the connected search MCP serverLimitations
It needs an LLM provider key in ~/.llm/config.json (or a custom base_url for a local model). Connected MCP servers run their own code and tools, and the config supports confirmation for sensitive ones. The project is small and updated infrequently.
How to disable. Uninstall the package: pip uninstall mcp-client-cli; the ~/.llm/config.json file can be removed manually.
FAQ
Which providers are supported?
Any LLM provider: OpenAI, Groq, a local model via llama and others, set in the config with an optional custom base_url.
Can I connect any MCP servers?
Yes. Servers are listed in the config with a launch command, args and env, and you can mark tools that require confirmation.
Discussion
No questions or reviews yet.
Related
CLI toolsA universal MCP CLI client from Apify: persistent sessions, OAuth, JSON output for scripts and shell access to any MCP server for agents
A CLI for any MCP server: list and call tools, resources and prompts, run mock and proxy modes, guard access and manage agent configs
A CLI that turns any MCP server, OpenAPI spec or GraphQL endpoint into commands at runtime, with no codegen
The mcpl CLI searches tools across several MCP servers and calls them from the terminal, with OAuth sign-in done by a human
A terminal MCP client for local Ollama models: MCP tools, prompts and resources, an agent mode and model switching
A Python framework and CLI for MCP: write servers as plain functions, test tools and install servers into Claude Code, Cursor and other clients
README in short
The README describes MCP CLI client as a simple command-line program that runs an LLM prompt and implements an MCP client. From the terminal you can connect any MCP-compatible servers, and the tool is framed as an alternative to Claude Desktop, supporting any provider including a local model via llama. Install is via pip, configured in ~/.llm/config.json: provider, model, key, an optional base_url and a list of MCP servers with commands, env and tool confirmation.