MCP Command Server

Created By
Andrew-Beniasha year ago
Overview

what is MCP Command Server?

MCP Command Server is a secure Model Context Protocol (MCP) server designed for executing system commands through LLM applications like Claude.

how to use MCP Command Server?

To use MCP Command Server, install the package using pip, configure the allowed commands, and integrate it with Claude Desktop configuration.

key features of MCP Command Server?

  • 🔒 Secure command execution with a whitelist of allowed commands.
  • ✅ User confirmation required for all commands to enhance security.
  • 📝 Comprehensive audit logging for tracking command executions.
  • 🔍 Input validation and sanitization to prevent malicious inputs.
  • 🤖 Integration with Claude Desktop for seamless operation.

use cases of MCP Command Server?

  1. Executing system commands securely in LLM applications.
  2. Providing a controlled environment for command execution.
  3. Enhancing security in automated systems that require command execution.

FAQ from MCP Command Server?

  • Is MCP Command Server secure?

Yes! It uses a whitelist approach and requires user confirmation for command execution.

  • How do I install MCP Command Server?

You can install it using pip with the command: uv pip install mcp-command-server.

  • Can I customize the allowed commands?

Yes! You can configure the allowed commands by setting the ALLOWED_COMMANDS environment variable.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Andrew-Beniash
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

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