Super Windows CLI MCP Server

Name: Super Windows CLI MCP Server
Author: Faucet94

@Faucet94

Super Windows CLI MCP Server について

Super Windows CLI Server, Fixed this "https://www.mcpmarket.com/server/super-windows-cli" as it is a mess to run on windows.

#super-win-cli #windows-cli #mcp-server

基本情報

カテゴリ

開発者ツール

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

Faucet94

設定

標準の設定はありません

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

リポジトリ

ツール

ツールは検出されませんでした

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

概要

What is Super Windows CLI MCP Server?

An enhanced fork of the Windows CLI MCP Server providing unrestricted, SYSTEM-level access to Windows environments via a command-line interface (MCP). It is intended for highly trusted environments where complete administrative control is required and security is managed externally.

How to use Super Windows CLI MCP Server?

Install Node.js 18+ and NSSM, clone the repository, copy NSSM.exe into the project root, run npm install, configure config.json, then execute .\install-service.ps1 as Administrator to install the MCPServer service. For manual testing, run npm run start in the project directory.

Key features of Super Windows CLI MCP Server

Unrestricted access to Windows shell environments (PowerShell, CMD, Git Bash)
Configurable command blocking and path restrictions
SYSTEM‑level service installation with NSSM for persistence
Automatic service recovery via NSSM
Disabled PowerShell telemetry for privacy
Process reuse for improved shell performance
Extended, configurable command timeouts

Use cases of Super Windows CLI MCP Server

Automating system‑administration tasks with full SYSTEM privileges
Running scripts across multiple Windows machines via optional SSH
Managing configuration and performing maintenance in isolated, trusted environments
Testing and debugging system‑level operations without permission barriers

FAQ from Super Windows CLI MCP Server

How does this server differ from the original win-cli-mcp-server?

It is an enhanced fork designed to run with unrestricted SYSTEM‑level access, offering complete control over the operating system but with significantly higher security risks.

What are the prerequisites?

Node.js version 18.0.0 or later and NSSM (Non‑Sucking Service Manager) are required. NSSM is used for reliable Windows service installation.

How is the server configured?

Configuration is stored in config.json, which contains security (e.g., allowedPaths, blockedCommands, commandTimeout), shells, and optional ssh sections. Modifying the security or shells key in config.json replaces the entire default section; the ssh section merges granularly.

How do I install the server as a Windows service?

Clone the repository, copy NSSM.exe into the root directory, run npm install, review and edit config.json, then execute .\install-service.ps1 from an administrative PowerShell. This creates a service named MCPServer that runs as LocalSystem and starts automatically.