cli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| addC | Add a new cli schema learned by traversing parsing all help menu subtrees. |
| helpC | Returns learned schema of cli. |
| runC | Run a command |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: add learns a CLI schema, help retrieves it, and run executes a command. There is no overlap.
All tool names are single imperative verbs (add, help, run), following a consistent pattern.
Three tools is appropriate for a focused CLI schema management server, covering learning, retrieval, and execution.
Basic lifecycle is covered (add, retrieve, run), but lacks schema update or deletion, and may not support multiple CLIs.