Windows Mcp

Created By
CursorToucha year ago
Lightweight MCP Server for easily automating Windows OS.
Overview

what is Windows-MCP?

Windows-MCP is a lightweight, open-source MCP server designed to automate tasks on the Windows operating system by integrating AI agents seamlessly.

how to use Windows-MCP?

To use Windows-MCP, set up the server by running the command {{PATH_TO_UV}} --directory {{PATH_TO_SRC}}/Windows-MCP run server.py and configure the necessary parameters in the server config file.

key features of Windows-MCP?

  • Seamless integration between AI agents and Windows OS
  • Automation of file navigation and application control
  • UI interaction capabilities
  • Support for QA testing and more tasks

use cases of Windows-MCP?

  1. Automating repetitive tasks in Windows applications
  2. Enhancing productivity through AI-driven file management
  3. Performing automated QA testing on Windows software

FAQ from Windows-MCP?

  • What is the purpose of Windows-MCP?

Windows-MCP serves to bridge the gap between AI agents and the Windows operating system, enabling automation of various tasks.

  • Is Windows-MCP free to use?

Yes! Windows-MCP is an open-source project and is free for everyone to use.

  • Can Windows-MCP be used for any Windows application?

Yes! Windows-MCP can interact with any Windows application that supports UI automation.

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

Recommend Servers

View All
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