windows-system

Windows System MCP provides a comprehensive interface for interacting with Windows systems via MCP. It exposes a suite of capabilities across file system management, process management, system information, registry operations, service management, network operations, and performance monitoring, enabling an AI agent or automation tool to browse directories, read and search files, view hardware and OS details, manage processes and services, query environment variables, perform network tests, and monitor real-time system metrics. The server is designed to be used with the Model Context Protocol (MCP) tooling, allowing you to issue structured actions and receive standardized results from the Windows host.

To use the server, install it globally or run via npx as described in the installation guide, then connect through the available MCP interfaces (stdio or SSE) depending on your integration. You can issue commands and actions such as list_directory, read_file, list_processes, get_system_overview, get_hardware_info, ping_host, scan_open_ports, and more, using the examples provided in the documentation. For SSE integration, configure the SSE endpoint to stream MCP interactions and results to your client, enabling real-time collaboration and monitoring.

Prerequisites:

• Windows 10/11
• Node.js 18+
• PowerShell 5.1+

Installation options:

Option A: Global installation (recommended)

1. Install the MCP server globally using npm:

npm install -g windows-system-mcp

2. Run the server directly:

windows-system-mcp

Option B: Run via npx without global install

npx windows-system-mcp

Option C: Build from source (if you prefer from GitHub)

1. Clone the repository and install dependencies:

git clone https://github.com/guangxiangdebizi/windows-system-mcp.git
cd windows-system-mcp
npm install

2. Build if required and start development/server as documented in the repo:

npm run build
npm start

Notes:

• Ensure you are running with appropriate permissions for Windows system access.
• If using SSE, you may need to start the SSE gateway separately as described in the deployment section of the project documentation.

Tips and considerations:

• For SSE deployments, start the server first, then connect via the SSE URL (e.g., http://localhost:3100/sse).
• The server supports multiple interfaces (stdio and SSE); choose the one that fits your orchestration workflow.
• When running in production, consider enabling auditing/logging to capture all MCP actions for security and traceability.
• Ensure your environment is secure; expose only necessary endpoints and apply least privilege principles for Windows management tasks.
• If you encounter path or permission issues, verify node version compatibility and run prompts with elevated privileges as needed.