mcp-bash-server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-bash-servercheck disk space usage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-bash-server
The problem
Cowork (and Claude Desktop) run in a sandbox and can't execute commands on your
own machine. This server bridges that gap — it connects Cowork to your local
bash so Claude can run shell commands directly on your computer, then read
their output.
Related MCP server: Bash MCP Server
What it is
A tiny Model Context Protocol server that lets
an MCP-aware client run shell commands on your local machine. It exposes one
tool, run_bash, and communicates over stdio.
From the client's side, running a command is just a tool call. On this side, the
command runs via bash -c with your user's permissions, and its exit code,
stdout, and stderr are returned.
⚠️ Security
By default this is an open shell: whatever connects can run anything you can. Only connect clients you trust, and consider using the allowlist below.
Install (easy way — double-click, no terminal)
Download mcp-bash-server.mcpb and double-click it. Claude Desktop opens an
install dialog — review the permissions, optionally set an allowlist and default
working directory, and click Install. That's it: no Terminal, no pip, no
config files. Claude Desktop manages the runtime for you, and because the server
is registered locally, it also becomes available inside Cowork sessions.
An
.mcpb(MCP Bundle) is the one-click install format for local MCP servers, like a browser extension. This bundle uses theuvruntime, so you don't even need Python pre-installed.
The rest of this README is the manual route, for development or if you'd rather run it yourself.
Requirements (manual route)
Python 3.10+
bashon yourPATH
Install
cd mcp-bash-server
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txtRun
The server supports two transports:
python server.py # stdio (default) — for the Claude Desktop bridge
python server.py --transport http # HTTP — serves MCP at http://127.0.0.1:8001/mcpstdio is the default. You normally don't run it by hand — the client launches it for you (see "Connect it to Claude Desktop" below). This is the simplest path: Claude Desktop runs the server as a subprocess and bridges it into Cowork automatically.
http serves the MCP streamable-http transport natively (no supergateway needed). Use it when you want to register the server as a custom connector by URL. Change host/port with
--host/--port.
Connect it to Claude Desktop
Add an entry to your claude_desktop_config.json
(macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"bash": {
"command": "/absolute/path/to/mcp-bash-server/.venv/bin/python",
"args": ["/absolute/path/to/mcp-bash-server/server.py"]
}
}
}Use absolute paths. Restart Claude Desktop; the run_bash tool should appear.
Connect it as a custom connector (HTTP / URL)
If you'd rather register it by URL (e.g. for Cowork's custom connector flow), run the HTTP transport and point the connector at it:
python server.py --transport http --port 8001
# -> serves http://127.0.0.1:8001/mcpThen add a custom connector with URL http://localhost:8001/mcp. To keep it
running across reboots, manage it with a process manager (e.g. pm2,
launchd, or systemd).
The tool
run_bash(command: str, cwd?: str, timeout?: int) → text with exit code, stdout,
stderr.
command— the shell command, run viabash -c.cwd— working directory (defaults to where the server started).timeout— seconds before the command is killed (capped byBASH_MCP_MAX_TIMEOUT).
Configuration (environment variables)
Variable | Default | Meaning |
| (unset) | Comma-separated command prefixes to allow, e.g. |
| server's cwd | Default working directory for commands. |
|
| Hard ceiling (seconds) on any command's runtime. |
|
|
|
|
| Bind host for |
|
| Bind port for |
Example — restrict to a safe set:
{
"mcpServers": {
"bash": {
"command": "/absolute/path/to/.venv/bin/python",
"args": ["/absolute/path/to/server.py"],
"env": { "BASH_MCP_ALLOWED": "git,ls,cat,grep,npm,node,python3" }
}
}
}Building the .mcpb yourself
npx @anthropic-ai/mcpb pack . mcp-bash-server.mcpbThis validates manifest.json and produces the installable bundle. The uv
server type means dependencies are resolved from pyproject.toml at install
time — nothing is vendored, so the same bundle works on macOS, Windows, and
Linux.
License
MIT — see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/uditk2/mcp-bash-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server