Shell Exec
● Activeio.github.domdomegg/shell-exec-mcp
Execute bash commands with background job support.
Connect this server
One click to install, or copy the config below. Suits: Claude Desktop · Cursor.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"shell-exec-mcp": {
"command": "npx",
"args": [
"-y",
"shell-exec-mcp@2.0.0"
]
}
}
}claude mcp add shell-exec-mcp -- npx -y shell-exec-mcp@2.0.0codex mcp add shell-exec-mcp -- npx -y shell-exec-mcp@2.0.0code --add-mcp '{"name":"shell-exec-mcp","type":"stdio","command":"npx","args":["-y","shell-exec-mcp@2.0.0"]}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Developer Tools
- Version
- 2.0.0
- Registry
- active
- Published
- 11/19/2026
Is it safe? Is it maintained?
Serverdex check: Nov 21, 2026Mostly fine: Shell Exec is maintained.
- Maintained
- Active
- Last commit 9 days ago (Nov 13, 2026), 1 open issues.
- Official registry
- Active
- Published as io.github.domdomegg/shell-exec-mcp in the official MCP registry, version 2.0.0.
- Source
- No licence found
- Public repository, but GitHub reports no recognised licence (9 stars). Check the README before shipping it in a product.
- Runs
- On your machine
- A local npm package started by your client; it can reach whatever your user account can.
- Credentials
- None declared
- The registry entry declares no required environment variables.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.
On GitHub
read Nov 18, 2026- Stars
- 9
- Forks
- 2
- Last push
- Nov 13, 2026
- License
- —
TypeScript
From the README
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. 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 Contributing Pull requests are welcomed on GitHub! To get started: 1. Install Git and Node.js 2. Clone the repository 3. Install dependencies with npm install 4. Run npm run test to run tests 5. Build with npm run build Releases Versions follow the semantic versioning spec. To release: 1. Use npm version to bump the version 2. Run git push --follow-tags to push with tags 3. Wait for GitHub Actions to publish to the NPM registry.
Read the full README on GitHub →Alternatives to Shell Exec
All Shell Exec alternatives →Best Developer Tools servers →The most-starred Developer Tools servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| REA | 466,935 | Nov 2026 | Local / not checked |
| GitHub | 34,658 | Nov 2026 | Needs sign-in |
| Repomix | 29,280 | Nov 2026 | Local / not checked |
| Compiler Explorer | 19,201 | Nov 2026 | Working |
| XERJ | 19,135 | Nov 2026 | Local / not checked |
Shell Exec: questions people ask
- Is Shell Exec a remote or a local MCP server?
- According to its entry in the official MCP registry, Shell Exec ships as a local package (npm) that your client starts on your machine.
- Is Shell Exec safe to use?
- Mostly fine: Shell Exec is maintained. In detail — maintained: Active; official registry: Active; source: No licence found; runs: On your machine; credentials: None declared. Serverdex check of Nov 21, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- Is Shell Exec still maintained?
- Active: the repository's last commit 9 days ago. Last push Nov 13, 2026, 9 GitHub stars. Read from GitHub on Nov 18, 2026.
- How do I add Shell Exec to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More from domdomegg
All 11 servers by domdomegg →- AirtableRead and write access to Airtable database schemas, tables, and records.Databases★ 456
- Computer UseControl your computer with screenshots, mouse, and keyboard automation.Media & Creative★ 406
- GmailAllow AI systems to read, send, archive, and manage emails via Gmail.Communication★ 12
- Starling BankAllow AI systems to view and control your Starling Bank account via MCP.Finance★ 8
More Developer Tools servers
Browse all Developer Tools →Letterbox
dovahkiin-v
File-based comms protocol for AI-to-AI dialogue between terminal agents.
LionScraper MCP + CLI + HTTP API (Node)
dowant
LionScraper Node: MCP stdio + CLI + HTTP API bridging AI to LionScraper browser extension.
LionScraper MCP + CLI + HTTP API (Python)
dowant
LionScraper Python: MCP stdio + CLI + HTTP API bridging AI to LionScraper browser extension.
AXIOM
dragoscv
Transactional write gate for coding agents: plan, canonical manifest, checks, two-phase apply.
Agentmako
drhalto
Local-first codebase intelligence MCP server for AI coding agents.
Mobilerun
droidrun
Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
Add the badge to your site
Show visitors that Shell Exec is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-domdomegg-shell-exec-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Shell Exec — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-domdomegg-shell-exec-mcp?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/io-github-domdomegg-shell-exec-mcp) [](https://serverdex.io/install/vscode/io-github-domdomegg-shell-exec-mcp) [](https://serverdex.io/install/claude-code/io-github-domdomegg-shell-exec-mcp)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/io-github-domdomegg-shell-exec-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-domdomegg-shell-exec-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-domdomegg-shell-exec-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).