Shell Command MCP Server

Created By
kaznaka year ago
This is an MCP (Model Context Protocol) server that allows executing shell commands within a Docker container. It provides a secure and isolated environment for running commands without giving access to the host Docker daemon.
Overview

What is Shell Command MCP Server?

Shell Command MCP Server is an MCP (Model Context Protocol) server that allows executing shell commands within a Docker container, providing a secure and isolated environment for running commands without giving access to the host Docker daemon.

How to use Shell Command MCP Server?

To use the Shell Command MCP Server, you need to have Docker installed. You can run the server by configuring your Docker command in your application, specifying the directory you want to mount to the container.

Key features of Shell Command MCP Server?

  • Execute shell scripts through a simple MCP interface with synchronous and asynchronous execution modes.
  • Includes Kubernetes tools like kubectl, helm, kustomize, and hemfile.
  • Runs in an isolated Docker container environment with non-root user access.
  • Allows host-container userid/groupid mapping for file ownership and permissions.
  • Supports mounting a host directory for persistence.

Use cases of Shell Command MCP Server?

  1. Running shell scripts in a secure environment.
  2. Managing Kubernetes resources using integrated tools.
  3. Providing a controlled workspace for AI applications that require shell command execution.

FAQ from Shell Command MCP Server?

  • Is the Shell Command MCP Server secure?

Yes! It runs as a non-root user and does not have access to the host Docker daemon, ensuring a secure execution environment.

  • What are the prerequisites to use this server?

You need to have Docker installed on your machine.

  • Can I use it on Windows?

Yes! The server can be configured to run on both MacOS and Windows.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kaznak
Star
3
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago