Shell 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 |
|---|---|
| terminalD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mcpreadme_desktop |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity about which tool to use.
With only one tool, naming consistency is not applicable; however, the name 'terminal' is a simple noun, which is acceptable but lacks a verb pattern.
A single tool for a shell server is too few; typical shell operations (e.g., run command, list files, manage processes) are all collapsed into one tool, making it overly broad and not well-scoped.
The tool surface is severely incomplete for a shell server, as it lacks explicit tools for common operations like file management, process control, or environment configuration, forcing the agent to rely on a single generic tool.