shell-command-mcp

Created By
egoista year ago
MCP server for executing shell commands.
Overview

what is shell-command-mcp?

The shell-command-mcp is a server designed for executing shell commands, allowing users to run commands in a controlled environment.

how to use shell-command-mcp?

To use shell-command-mcp, you can either configure it manually using the command npx -y shell-command-mcp or set up a JSON configuration to specify allowed commands and their arguments.

key features of shell-command-mcp?

  • Execute shell commands securely with specified permissions.
  • Customizable command execution through JSON configuration.
  • Environment variable support for command restrictions.

use cases of shell-command-mcp?

  1. Running shell commands in a controlled environment for automation tasks.
  2. Integrating with other applications that require command execution capabilities.
  3. Providing a secure way to execute commands without exposing the system to risks.

FAQ from shell-command-mcp?

  • What commands can I run with shell-command-mcp?

You can run commands specified in the ALLOWED_COMMANDS environment variable.

  • Is it safe to allow all commands?

Allowing all commands using * can be dangerous and is not recommended.

  • How do I configure allowed commands?

You can configure allowed commands by setting the ALLOWED_COMMANDS environment variable in the JSON configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
egoist
Star
6
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

6 hours ago