command-executor MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Command Executor MCP Server?

Command Executor MCP Server is a Model Context Protocol server designed for executing pre-approved commands securely, ensuring that only safe commands are executed in a controlled environment.

how to use Command Executor MCP Server?

To use the Command Executor MCP Server, install the necessary dependencies, build the server, and configure the allowed commands through environment variables. You can then execute commands via the provided API.

key features of Command Executor MCP Server?

  • Secure command execution with a pre-approved command list
  • Configurable allowed commands through environment variables
  • Built with TypeScript and MCP SDK
  • Real-time command output streaming
  • Comprehensive error handling and security validations

use cases of Command Executor MCP Server?

  1. Executing development commands in a secure environment.
  2. Integrating with desktop applications for command execution.
  3. Providing a controlled interface for executing scripts and commands.

FAQ from Command Executor MCP Server?

  • What commands can be executed?

Only commands that are pre-approved and listed in the configuration can be executed.

  • How do I customize the allowed commands?

You can customize the allowed commands by setting the ALLOWED_COMMANDS environment variable.

  • Is the server secure?

Yes! The server implements several security measures, including command validation and environment isolation.

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