system-command-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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_environmentA | Return the authoritative system execution environment and registered logical program names. Program availability is already reflected in system_exec; do not probe with which, where, command -v, or Get-Command. |
| system_execA | Execute one registered system program directly through a cross-platform program-and-arguments interface. Use only program names in the enum. Pass arguments separately without shell quoting. Shell operators, pipelines, redirects, command substitution, and environment expansion are not supported. Do not probe or guess alternative executable names. |
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 2 tools
system_environment provides information about the execution environment and registered program names, while system_exec actually executes a program. Their purposes are completely distinct with no overlap, making selection unambiguous.
Both tools follow a consistent 'system_' prefix pattern in snake_case. Although 'environment' is a noun and 'exec' is a verb, the uniform prefix and clear naming make the pattern predictable.
With only two tools, the server feels minimal and borderline thin for even a focused command-execution utility. The count is not egregiously low, but it leaves little room for additional useful operations.
The two tools cover the core needs of querying the environment and executing registered programs. Minor gaps exist, such as no capability to manage program registrations or handle interactive sessions, but these are likely beyond the server's intended scope.