Skip to main content
Glama

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

execute

Run a bash command (with optional timeout and background mode)

get_job_status

Check 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.

Available Tools

2 tools
executeExecuteA

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

    A3.8/5.0

    Scored across 2 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      Enables 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
      -
    • F
      license
      A
      quality
      C
      maintenance
      Provides 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
      -