Linux 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_bash_commandC | Execute a bash command in WSL2 Linux environment |
| execute_bash_scriptC | Execute a bash script file in WSL2 Linux environment |
| create_bash_scriptC | Create a bash script file with specified content |
| list_directoryB | List contents of a directory in WSL2 Linux environment |
| get_system_infoB | Get system information about the WSL2 Linux environment |
| check_wsl_statusB | Check WSL2 status and get distribution information |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity: checking WSL status, creating scripts, executing commands, executing scripts, getting system info, and listing directories. The descriptions clearly differentiate between command execution, script handling, and system operations.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., check_wsl_status, execute_bash_command). The naming convention is uniform throughout the set, making it predictable and easy to understand.
With 6 tools, this is well-scoped for a Linux/bash server focused on WSL2 operations. Each tool earns its place by covering essential functions like command execution, script management, and system inspection without being overwhelming or too sparse.
The toolset provides good coverage for core WSL2/bash operations, including execution, scripting, and system info. A minor gap exists in file manipulation (e.g., create/delete files beyond scripts) and process management, but agents can work around this using existing tools like execute_bash_command.