MCP.so
ログイン

Windows Terminal MCP Server

@2bytes-org

基本情報

カテゴリ

開発者ツール

トランスポート

stdio

作者

2bytes-org

Windows Terminal MCP Server について

MCP сервер для выполнения команд в терминале Windows через REST API

Windows Terminal MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Windows Terminal MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Windows Terminal MCP Server?

Windows Terminal MCP Server is a REST API server that executes Windows terminal commands. It can be run locally or in a Docker container and supports a secure mode with a restricted set of commands. Designed for developers and administrators who need remote or automated command execution on Windows.

How to use Windows Terminal MCP Server?

Clone the repository, configure an API key via a .env file or environment variable, then launch using the provided batch scripts or manually with npm start. The server exposes endpoints at POST /execute and POST /execute-safe (secure mode) along with a health check at GET /health. All requests (except health) require the x-api-key header.

Key features of Windows Terminal MCP Server

  • REST API to execute arbitrary Windows commands
  • Secure mode limiting commands to a safe subset
  • Deployable locally or inside a Windows Docker container
  • API‑key authentication for access control
  • Health-check endpoint for monitoring
  • Test script included to verify API functionality

Use cases of Windows Terminal MCP Server

  • Remotely run Windows CLI commands from any HTTP client
  • Integrate terminal execution into automation scripts or CI/CD pipelines
  • Securely expose limited command execution (e.g., dir, systeminfo) to other services
  • Containerized deployment for isolated command execution in Windows environments

よくある質問

1

Why is an API key required?

The API key prevents unauthorized access to the terminal. It must be set via environment variable or configuration before starting the server.

2

What are the runtime requirements for local deployment?

Node.js 14.x or higher and npm 6.x or higher are required. For Docker, Windows 10/11 with Docker Desktop configured for Windows containers is needed.

3

What commands are allowed in secure mode?

Only `dir`, `echo`, `type`, `ver`, `systeminfo`, and `tasklist` are permitted in the `execute-safe` endpoint.

4

Can the server be exposed to the internet?

The README advises against exposing the server to external networks without additional security measures and recommends using a strong, unique API key.

5

Which transport and authentication methods are used?

The server communicates via HTTP and authenticates every non‑health request using an API key passed in the `x-api-key` header.

コメント

「開発者ツール」の他のコンテンツ