Shell Execution MCP Server

Created By
samihalawaa year ago
Shell Execution MCP Server for Claude and other MCP-compatible AI assistants
Overview

what is Shell Execution MCP Server?

Shell Execution MCP Server is a Model Context Protocol (MCP) server that provides persistent shell command execution capabilities for Claude and other MCP-compatible AI assistants.

how to use Shell Execution MCP Server?

To use the Shell Execution MCP Server, clone the repository, install dependencies, build the server, and start it. Configure it in your MCP settings to enable command execution.

key features of Shell Execution MCP Server?

  • Persistent Shell Session: Maintains state between commands in the same session.
  • Background Execution: Run commands in the background with proper process management.
  • Cross-Platform: Works on macOS, Linux, and Windows.
  • Timeout Control: Configure command execution timeouts.
  • Session Reset: Ability to reset the shell session if needed.

use cases of Shell Execution MCP Server?

  1. Execute shell commands in a persistent environment.
  2. Run long-running processes in the background.
  3. Manage shell sessions for AI assistants.

FAQ from Shell Execution MCP Server?

  • Can I run commands in the background?

Yes! You can run commands in the background with the appropriate configuration.

  • Is it compatible with all operating systems?

Yes! It works on macOS, Linux, and Windows.

  • How do I reset the shell session?

You can reset the shell session using the reset-shell command.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
samihalawa
Star
0
Language
TypeScript
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