mcp-bash
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 |
|---|---|
| set_cwdA | |
| execute_bashA | |
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
The two tools have clearly distinct purposes: one sets the working directory, the other executes commands. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun pattern: set_cwd and execute_bash. The naming is predictable and consistent.
With only two tools, the set is minimal yet sufficient for its scope. Each tool serves a necessary function without unnecessary bloat.
The core functionality of a bash server is covered: setting the working directory and executing commands. Minor gaps like environment variable management exist but are not critical for basic operations.