Shell Exec MCP
Click on "Deploy 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., "@Shell Exec MCP run 'find . -name *.log' to list all log files"
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.
shell-exec-mcp
MCP server for executing bash commands with background job support.
Use Cases
Run build commands: Execute npm run build, make, or other build tools and get the output.
File operations: Use find, grep, mv, rm, mkdir -p, stat etc. for file management.
Long-running tasks: Start servers or watch processes in background mode, check on them later.
System info: Run df -h, ps aux, env etc. to inspect the system state.
Related MCP server: Run Command MCP Server
Setup
Follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).
Tools
Tool | Description |
| Run a bash command (with optional timeout and background mode) |
| Check status of a background job |
Contributing
Pull requests are welcomed on GitHub! To get started:
Install Git and Node.js
Clone the repository
Install dependencies with
npm installRun
npm run testto run testsBuild with
npm run build
Releases
Versions follow the semantic versioning spec.
To release:
Use
npm version <major | minor | patch>to bump the versionRun
git push --follow-tagsto push with tagsWait for GitHub Actions to publish to the NPM registry.
Available Tools
2 toolsexecuteExecuteA
Run a command in bash.
Returns stdout, stderr, and exit code. Default timeout is 5 seconds.
For long-running commands, set 'background: true' to run in background and get a job ID. Then use get_status to check on it.
Tips:
Use background mode for commands that take more than a few seconds
For file searches, use 'find' or 'grep'
For file operations, use 'mv', 'rm', 'mkdir -p', 'stat' etc.
Inputs: command (required), background, timeout_ms.
get_job_statusGet Job StatusA
Check status of a background job.
Returns stdout/stderr collected so far, exit code (null if still running), and whether the job is still running.
Completed jobs are cleaned up after their status is read.
Inputs: jobId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have largely distinct purposes: execute runs commands while get_job_status polls background jobs. However, the execute description refers to 'get_status' while the actual tool is named 'get_job_status', which could cause an agent to call a non-existent tool.
The set mixes a bare verb ('execute') with a verb_noun pattern ('get_job_status'), and the description further muddies this by referencing a third name ('get_status'). It is still readable but not a predictable pattern.
Two tools is minimal but reasonably matched to the narrow shell-execution scope, since running a command and checking job status are the two essential operations. It sits just under the typical 3-15 range.
Running commands and polling background jobs are covered, but there is no way to kill or cancel a long-running job, nor to list active jobs. These are notable gaps for a process-execution server where runaway commands are a common failure mode.
Maintenance
Related MCP Connectors
I run shell commands on your private cloud environment (bash, sh, zsh)
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables safe execution of system shell commands with real-time streaming output and rich metadata capture. Provides configurable command execution with timeout controls, environment management, and extensible plugin architecture for monitoring command lifecycles.4-
- FlicenseAqualityCmaintenanceProvides tools for executing shell commands both synchronously and asynchronously with real-time output streaming and process management capabilities. It enables users to start background tasks, monitor progress, and manage long-running processes via Stdio or HTTP transports.3-
- AlicenseAqualityFmaintenanceEnables executing shell commands without permission prompts, including running commands and managing background processes.411MIT
- FlicenseNot gradedqualityDmaintenanceEnables Open WebUI to execute bash commands for coding tasks in a persistent projects workspace, with configurable timeouts and output limits.-