Bash 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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bash_execA | Execute a bash command and return stdout, stderr, exit code, and duration. |
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
There is only one tool, so there is no possibility of overlap or confusion between tools. Its purpose is clear and distinct: executing bash commands.
With a single tool, there is no inconsistent naming to worry about. The name 'bash_exec' follows a clear verb_noun pattern and accurately describes its function.
A single tool is on the thin side, but for a focused bash execution server it may be sufficient. However, the minimal surface area limits flexibility and discoverability.
The tool covers the full apparent scope of the server: executing bash commands and returning outputs, errors, exit codes, and duration. There are no obvious missing operations for this narrow domain.