Super Windows CLI MCP Server

Created By
Faucet94a year ago
Super Windows CLI Server, Fixed this "
Overview

What is Super Windows CLI MCP Server?

Super Windows CLI MCP Server is an enhanced fork of the Windows CLI MCP Server that provides unrestricted system access to Windows environments via a command-line interface (MCP).

How to use Super Windows CLI MCP Server?

To use the server, install it as a persistent Windows service with SYSTEM-level privileges using NSSM, and configure the settings in config.json to ensure security and functionality.

Key features of Super Windows CLI MCP Server?

  • Complete access to Windows shell environments (PowerShell, CMD, Git Bash).
  • Unrestricted command execution and full file system access.
  • SYSTEM-level service installation for persistence and auto-recovery.
  • Network binding controls and disabled PowerShell telemetry for enhanced privacy.
  • Extended timeouts for long-running operations.

Use cases of Super Windows CLI MCP Server?

  1. Running administrative scripts in a controlled environment.
  2. Automating tasks that require SYSTEM-level access.
  3. Debugging and testing applications that interact with the Windows shell.

FAQ from Super Windows CLI MCP Server?

  • Is it safe to run this server?

Only run this server in highly trusted environments where you have full control over network access due to its SYSTEM-level privileges.

  • What are the prerequisites for installation?

You need Node.js (version 18.0.0 or later) and NSSM (Non-Sucking Service Manager) installed.

  • How can I uninstall the server?

You can uninstall the server by running the uninstallation script provided in the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Faucet94
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago