Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Bash Command MCP

by mrorigoversion 1.0.0i★ –iRuns on your computer
Registry nameio.github.mrorigo/bash-command-mcp

Install

Overview

Description from the maker (original English)

Sophisticated bash command MCP server that runs and manages shell execution.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: OTEL_ENABLED, OTEL_SERVICE_NAME, OTEL_SERVICE_VERSION, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_METRIC_EXPORT_INTERVAL_MS, BASH_COMMAND_MCP_LOG_DIR

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "bash-command": {
      "command": "npx",
      "args": [
        "-y",
        "bash-command-mcp"
      ],
      "env": {
        "OTEL_ENABLED": "your-value",
        "OTEL_SERVICE_NAME": "your-value",
        "OTEL_SERVICE_VERSION": "your-value",
        "OTEL_EXPORTER_OTLP_ENDPOINT": "your-value",
        "OTEL_METRIC_EXPORT_INTERVAL_MS": "your-value",
        "BASH_COMMAND_MCP_LOG_DIR": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add bash-command --env OTEL_ENABLED=your-value --env OTEL_SERVICE_NAME=your-value --env OTEL_SERVICE_VERSION=your-value --env OTEL_EXPORTER_OTLP_ENDPOINT=your-value --env OTEL_METRIC_EXPORT_INTERVAL_MS=your-value --env BASH_COMMAND_MCP_LOG_DIR=your-value -- npx -y bash-command-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "bash-command": {
      "command": "npx",
      "args": [
        "-y",
        "bash-command-mcp"
      ],
      "env": {
        "OTEL_ENABLED": "your-value",
        "OTEL_SERVICE_NAME": "your-value",
        "OTEL_SERVICE_VERSION": "your-value",
        "OTEL_EXPORTER_OTLP_ENDPOINT": "your-value",
        "OTEL_METRIC_EXPORT_INTERVAL_MS": "your-value",
        "BASH_COMMAND_MCP_LOG_DIR": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "bash-command": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "bash-command-mcp"
      ],
      "env": {
        "OTEL_ENABLED": "your-value",
        "OTEL_SERVICE_NAME": "your-value",
        "OTEL_SERVICE_VERSION": "your-value",
        "OTEL_EXPORTER_OTLP_ENDPOINT": "your-value",
        "OTEL_METRIC_EXPORT_INTERVAL_MS": "your-value",
        "BASH_COMMAND_MCP_LOG_DIR": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • OTEL_ENABLED env
    Enable or disable OpenTelemetry instrumentation (`true` or `false`).
  • OTEL_SERVICE_NAME env
    OpenTelemetry service name override.
  • OTEL_SERVICE_VERSION env
    OpenTelemetry service version override.
  • OTEL_EXPORTER_OTLP_ENDPOINT env
    OTLP HTTP endpoint for exporting OpenTelemetry traces and metrics (for example `http://localhost:4318`).
  • OTEL_METRIC_EXPORT_INTERVAL_MS env
    OpenTelemetry metrics export interval in milliseconds.
  • BASH_COMMAND_MCP_LOG_DIR env
    Directory used to store background process stdout/stderr log files.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mrorigo, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32384 servers in this category
  • Published to the registry more recently than 2% of the other 32384 servers in this category
  • Basic checks equal to or better than 100% of the other 32384 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Bash Command MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, 오늘냥이 (Oneul Nyangi)

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

bash-command-mcp

A highly sophisticated Bash MCP server for safe, structured command execution with first-class background job orchestration.

Important Security Warning

This server executes shell commands on the machine where it is running.

If you run bun run index.ts directly on your host, commands run on your host with your user permissions. Use Docker to isolate execution unless you fully trust the MCP client and prompts.

To install dependencies:

bun install

To run over stdio:

bun run index.ts

To run over Streamable HTTP:

BASH_COMMAND_MCP_TRANSPORT=http \

BASH_COMMAND_MCP_HOST=127.0.0.1 \ BASH_COMMAND_MCP_PORT=3000 \ bun run index.ts

To run via npm/npx (published package):

npx -y bash-command-mcp

Why This Server

  • High-fidelity shell execution with clear exit-code semantics.
  • Advanced background process lifecycle controls (run_background, wait_background, kill_background).
  • Built-in observability via per-process stdout/stderr log files.
  • OpenTelemetry traces and metrics for production visibility.
  • Agent-friendly ergonomics with cwd and env overrides for precise execution context.

Tool Behavior

Tools:

  • run: run command in foreground. Args: command or cmd, timeoutSeconds (default 60, min 1; values above 86400 are capped with a hint), optional cwd, optional env.
  • run_background: start command in background with stdout/stderr written to log files. Args: command or cmd, optional cwd, optional env.
  • 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. Args: pid, optional lines (default 200, max 5000).
  • wait_background: wait for background process completion and return final status/output. Args: pid, optional timeoutSeconds (default 60, min 1; values above 86400 are capped with a hint).

OpenTelemetry

This server includes built-in OpenTelemetry instrumentation for traces and metrics.

  • OpenTelemetry packages are installed with the server package.
  • Telemetry initializes unless OTEL_ENABLED=false.
  • If OTEL_EXPORTER_OTLP_ENDPOINT is set, traces/metrics are exported via OTLP HTTP.
  • If no OTLP endpoint is configured, console exporters are used.

Instrumented operations:

  • Tool call spans for run, run_background, list_background, tail_background, wait_background, and kill_background.
  • Background lifecycle spans/counters (started, ended).
  • Metrics for tool calls, failures, timeouts, and duration histograms.

Common env vars:

  • OTEL_ENABLED=true|false
  • OTEL_SERVICE_NAME=bash-command-mcp
  • OTEL_SERVICE_VERSION=1.0.0
  • OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318
  • OTEL_METRIC_EXPORT_INTERVAL_MS=10000
  • BASH_COMMAND_MCP_LOG_DIR=/path/to/log-dir

Example (OTLP Collector on localhost):

OTEL_ENABLED=true \

OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 \ OTEL_SERVICE_NAME=bash-command-mcp \ npx -y bash-command-mcp

Transports

This server supports two transports:

  • stdio for local, process-spawned integrations.
  • http for remote or network-accessible MCP clients using Streamable HTTP.

Default behavior remains stdio so existing desktop and CLI setups keep working.

Environment variables for HTTP mode:

  • BASH_COMMAND_MCP_TRANSPORT=http|stdio
  • BASH_COMMAND_MCP_HOST=127.0.0.1
  • BASH_COMMAND_MCP_PORT=3000
  • BASH_COMMAND_MCP_ALLOWED_HOSTS=localhost,127.0.0.1,[::1]

HTTP mode uses host-header validation by default when bound to a loopback address. If you bind to 0.0.0.0 or ::, provide an explicit allow-list in BASH_COMMAND_MCP_ALLOWED_HOSTS.

Docker

Build the image:

docker build -t bash-command-mcp .

Run with a local folder mounted at /workspace:

docker run --rm -i -v "$(pwd):/workspace" bash-command-mcp

Run over Streamable HTTP:

docker run --rm -p 3000:3000 \

-e BASH_COMMAND_MCP_TRANSPORT=http \ -e BASH_COMMAND_MCP_HOST=0.0.0.0 \ -e BASH_COMMAND_MCP_PORT=3000 \ bash-command-mcp

/workspace mapping explained:

  • Left side ($(pwd)) is a folder on your host machine.
  • Right side (/workspace) is the path inside the container.
  • Commands run by this MCP server should target files under /workspace; those changes are written back to the mapped host folder.

For HTTP mode in Docker, bind to 0.0.0.0 and publish the port with -p. If you expose the container beyond localhost, set BASH_COMMAND_MCP_ALLOWED_HOSTS to the hostnames you want to permit.

Example:

  • If your host has ./project/file.txt and you run the container from ./project, the same file is available in the container at /workspace/file.txt.
Ask PopNx