Super Windows CLI MCP Server

Created By
MCP-Mirrora year ago
Mirror of
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 capabilities for trusted environments.

how to use Super Windows CLI MCP Server?

To use the server, build the project using npm, copy the built files to your Windows machine, and run the installation script as an administrator.

key features of Super Windows CLI MCP Server?

  • Full system access through SYSTEM service installation
  • Unrestricted command execution
  • Complete access to Windows shell environments (PowerShell, CMD, Git Bash)
  • Automatic service recovery and fault tolerance
  • Network-level access controls

use cases of Super Windows CLI MCP Server?

  1. Running administrative tasks without command restrictions
  2. Managing system processes with full access
  3. Implementing network-level security in trusted environments

FAQ from Super Windows CLI MCP Server?

  • Is this server safe to use?

It is designed for trusted environments where full system access is required, but caution is advised due to the removal of application-level restrictions.

  • How do I install the server?

Build the project, copy the files to your Windows machine, and run the installation script as administrator.

  • What are the network security features?

The server includes localhost binding, configurable allowed IP ranges, and local network restrictions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days 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)

12 hours ago
Crevio

a day ago