Windows Terminal MCP Server

@2bytes-org

Repository

Basic information

About Windows Terminal MCP Server

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

Windows Terminal MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Windows Terminal MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

Frequently asked questions

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.

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.

What commands are allowed in secure mode?

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

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.

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.

Comments

More Developer Tools MCP servers

GripForge

gripforgeai

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Mcp-Warden

ermoluk

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

FARPY

mangomunchr

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

Modelglass

Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott

SSH MCP Server

hypnosis

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.