About CLI MCP
CLI MCP is an MCP server published by mlaugharn in the AI category: cli-based program to run llm prompt and mcp. It has been installed 0 times through Conduid.
The repository has 8 stars and 1 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx cli-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about CLI MCP
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
cli MCP server
cli bridge
Pretty much a remix of the demo notes app.
Components
Resources
The server implements a simple system for working with arbitrary clis with:
- Custom cli:// URI scheme for accessing individual notes
- Each cli resource has a name, help menu subtree, and text/plain mimetype
Tools
The server implements one tool:
- add (cmd): Recursively parses cli help menu subtrees and stores definition
- Takes "cmd"
- Updates server state and notifies clients of resource changes
- help (cmd): Return subtrees definition
- run (cmd, cmd_args | None): Run a known command
Quickstart
Install
Claude Desktop
Note: I had to use /opt/homebrew/bin/uv instead of just uv in the command field in this json:
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{"mcpServers": {
"cli": {
"command": "uv",
"args": [
"run",
"--directory",
"\<path to repo folder\>",
"cli"
]}
}
}
By design, you have to explicitly 'add' a command before it can be run.
Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory <path to repo> run cli
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
README mirrored from the source repository 5 months ago. The original is authoritative.