🖥️ Shell MCP Server

Created By
blazickjpa year ago
Secure shell command execution MCP server for Claude AI. Enables controlled shell access within specified directories.
Overview

What is Shell MCP Server?

Shell MCP Server is a secure command execution server designed for AI applications, particularly for Claude AI, allowing controlled execution of shell commands within specified directories.

How to use Shell MCP Server?

To use Shell MCP Server, install it via pip, configure your Claude Desktop application with the provided settings, and execute commands within allowed directories.

Key features of Shell MCP Server?

  • Secure Execution: Commands can only run in specified directories.
  • Multiple Shell Support: Compatible with bash, sh, cmd, and powershell.
  • Timeout Control: Automatically terminates long-running commands.
  • Cross-Platform: Functions on both Unix and Windows systems.
  • Safety Features: Built-in validation for directories and shells ensures security.

Use cases of Shell MCP Server?

  1. Executing file system commands like listing or searching files.
  2. Performing project management tasks including Git operations and package management.
  3. Monitoring system resources and processes securely.
  4. Running scripts with controlled dependencies in specified environments.

FAQ from Shell MCP Server?

  • Can I execute any command using Shell MCP Server?

No, only commands within specified allowed directories will execute to ensure security.

  • How do I install Shell MCP Server?

You can install it using pip with the command 'pip install shell-mcp-server'.

  • Is Shell MCP Server free to use?

Yes, it is open-source and licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
blazickjp
Star
-
Language
-
License
-
Tags

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)

2 days ago