Secure Command Executor MCP Server

@HappyAny

代码仓库

基本信息

分类

其他

许可证

MIT

传输方式

stdio

作者

HappyAny

关于 Secure Command Executor MCP Server

A robust command execution service with daily log rotation, designed to securely manage and execute system commands with safety checks and logging.

#secure-command-executor#command-execution#system-management

Secure Command Executor MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "secure-command-executor-mcp-server": {
      "command": "node",
      "args": [
        "index.js",
        "--file",
        "commands.json",
        "--logs",
        "logs",
        "--port",
        "3000"
      ]
    }
  }
}

Secure Command Executor MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Secure Command Executor MCP Server?

A robust command execution MCP service with daily log rotation, designed to securely manage and execute system commands with safety checks and logging. It is intended for developers or system administrators who need controlled, auditable command execution through the Model Context Protocol.

How to use Secure Command Executor MCP Server?

Clone the repository, install dependencies (minimist, @modelcontextprotocol/sdk, zod), configure commands.json, and start the service with node index.js --file commands.json --logs logs --port 3000. Integrate it via MCP settings by specifying the script path and arguments. Use the provided HTTP API endpoints to execute, manage, and query commands and logs.

Key features of Secure Command Executor MCP Server

Execute system commands with optional arguments.
Safety checks and confirmation prompts for dangerous commands.
Add, update, remove, enable, or disable commands.
Daily log rotation with detailed action tracking.
Query commands and logs with filters.

Use cases of Secure Command Executor MCP Server

Safely executing system commands through an MCP server.
Managing a controlled set of allowed commands.
Auditing command execution history with log rotation.
Preventing accidental dangerous commands via confirmation prompts.
Querying available commands and their statuses.

常见问题

How does the server handle dangerous commands?

Commands marked as `dangerous: true` trigger a warning and require explicit confirmation before execution, based on the `confirmationPrompt` and `consequences` fields defined in `commands.json`.

Where are logs stored and how are they rotated?

Logs are stored in the directory specified by the `--logs` argument (default `logs`). Each day’s logs are saved in a separate file named `YYYY-MM-DD.json`, achieving daily rotation.

How can I configure the available commands?

Modify the `commands.json` file to define command names, descriptions, examples, danger flags, and enabled status. Alternatively, use the `/manageCommand` API endpoint to add, update, or remove commands at runtime.

What dependencies are required to run the server?

The server requires Node.js and the npm packages `minimist`, `@modelcontextprotocol/sdk`, and `zod`. These are installed via `npm install`.

Can I change the port or other runtime settings?

Yes, use command-line arguments `--port` (default 3000), `--file` for commands path, and `--logs` for logs directory. Environment variables `PORT` and `NODE_ENV` are also supported.

其他分类下的更多 MCP 服务器

EverArt

modelcontextprotocol

Model Context Protocol Servers

88.1K

Health by Dr Brad

Dr Brad Stanfield

Health by Dr Brad works out a health plan from your own results: which screening is due at your age, and evidence-based suggestions, each with the reason and the published guideline or study behind it. Your record is one

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.