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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

12 hours ago
Voyei

an hour ago