Shell MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Shell MCP Server?

Shell MCP Server is a Model Context Protocol server designed to allow Large Language Models (LLMs) to execute shell commands and retrieve outputs securely.

How to use Shell MCP Server?

You can use Shell MCP Server by running it directly with uvx or installing it via pip. After installation, configure it for your development environment to execute commands.

Key features of Shell MCP Server?

  • Executes shell commands and returns the output.
  • Provides command results including stdout, stderr, and return code.
  • Configurable to work with different applications like Claude and Zed.

Use cases of Shell MCP Server?

  1. Automating command execution in development environments.
  2. Integrating shell command capabilities into AI applications.
  3. Safely managing system commands from LLM interactions.

FAQ from Shell MCP Server?

  • Is this server safe to use?

⚠️ Use with caution as it executes shell commands directly. Implement security measures to prevent unauthorized access.

  • How can I install the Shell MCP Server?

Install via pip with pip install mcp-server-shell or run directly using uvx without installation.

  • Can I contribute to the project?

Yes! Contributions are welcome to enhance the server and improve functionality.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

2 days ago
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