Shell 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.
A simple MCP server that provides a terminal tool for executing shell commands.
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 |
|---|---|
| terminalB | |
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
With only one tool, there is no possibility of confusing it with another. Its purpose—execute a shell command—is explicit and unambiguous.
A single tool cannot exhibit inconsistency, and 'terminal' is clear and readable. It is a noun rather than a verb_noun action name, so it does not fully follow the ideal convention.
A shell server naturally needs only one general-purpose execution tool, so the count is well-scoped rather than bloated. It is on the thin side, but additional tools would likely be redundant wrappers.
Because arbitrary shell commands can cover file operations, process control, and environment inspection, the surface is functionally broad. Minor gaps exist around streaming output, session persistence, and structured error handling, but these are workable via shell.