Sophisticated bash command MCP server that runs and manages shell execution.
Connect Bash to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Sophisticated bash command MCP server that runs and manages shell execution. The bash mcp server is what makes that connection.
A highly sophisticated Bash MCP server for safe, structured command execution with first-class background job orchestration.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
High — fidelity shell execution with clear exit-code semanticsBuilt — in observability via per-process stdout/stderr log filesAgent — friendly ergonomics with cwd and env overrides for precise execution contextrun — run command in foregroundrun_background — start command in background with stdout/stderr written to log fileslist_background — list tracked background processes, including log file pathskill_background — stop tracked background process by pidtail_background — show last N lines from background process logswait_background — wait for background process completion and return final status/outputbash-command-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: BASH_COMMAND_MCP_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Bash's toolset — High, Built, Agent and 6 more — is a fair guide to whether it matches your workflow. It is maintained by mrorigo; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| High | fidelity shell execution with clear exit-code semantics. |
| Built | in observability via per-process stdout/stderr log files. |
| Agent | friendly ergonomics with cwd and env overrides for precise execution context. |
| run | run command in foreground. |
| run_background | start command in background with stdout/stderr written to log files. |
| list_background | list tracked background processes, including log file paths. |
| kill_background | stop tracked background process by pid. |
| tail_background | show last N lines from background process logs. |
| wait_background | wait for background process completion and return final status/output. |
{
"mcpServers": {
"bash-command": {
"command": "npx",
"args": ["-y", "bash-command-mcp"],
"env": {
"BASH_COMMAND_MCP_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| BASH_COMMAND_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.