MCP.so
ログイン

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.

よくある質問

1

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`.

2

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.

3

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.

4

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`.

5

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.

コメント

「その他」の他のコンテンツ