Terminal MCP Server
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_commandC | |
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 1 tool
Only one tool exists, so there is no possibility of confusion. The tool's purpose is clearly defined as running a terminal command.
The tool name 'run_command' follows a clear verb_noun pattern, which is consistent and intuitive. Even with a single tool, the naming is descriptive and unambiguous.
A single tool is minimal, but it directly fulfills the server's stated purpose of executing terminal commands. The count is slightly below the typical range but well-scoped for the narrow domain.
The server's entire purpose is to run terminal commands, and the single tool fully covers this operation. There are no missing capabilities for the defined scope.