Shell Exec

io.github.domdomeggPublished by GitHub account domdomeggv1.2.0Updated Oct 24, 2026

Execute bash commands with background job support.

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets an assistant run bash commands on your machine, including long-running jobs in the background.

What you can do
  • Run arbitrary bash commands, optionally with a timeout or in background mode
  • Check the status of background jobs started earlier
  • Run build tools and capture their output
  • Perform file operations through shell utilities such as find, grep, mv, rm, mkdir and stat
  • Inspect system state with commands like df, ps and env
When to use it
Useful when you want an assistant to build projects, manage files, inspect system state, or start and monitor long-running processes such as dev servers on your own machine.
Requirements
Runs as a local stdio process, launched with npx from the npm package shell-exec-mcp, so Node.js and npm are needed. The MCP_TRANSPORT environment variable is required. No authentication is declared. Desktop client only.
Before you install
It executes arbitrary bash commands with your user's permissions, including destructive ones such as rm, and can read environment variables that may hold secrets. Background jobs keep running after the call returns. Only install it if you trust the assistant and the commands it will issue.

Installation

In SourceWeft

  1. Open Shell Exec in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

ToolDescription
executeRun a bash command (with optional timeout and background mode)
get_job_statusCheck status of a background job

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 <major | minor | patch> 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.

Source: README.md at commit 4f23013

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.