MCPControl

Created By
Cheffromspacea year ago
MCP server for Windows OS automation
Overview

What is MCPControl?

MCPControl is a cross-platform control server for the Model Context Protocol (MCP), designed to provide programmatic control over system operations such as mouse, keyboard, window management, and screen capture functionality.

How to use MCPControl?

To use MCPControl, clone the repository from GitHub, install the necessary dependencies, build the project, and configure it with your MCP servers. After configuration, restart your MCP server to access the MCPControl service.

Key features of MCPControl?

  • Window management capabilities including listing, focusing, and resizing windows.
  • Mouse control with configurable speed, click operations, and cursor tracking.
  • Keyboard control for text input and key operations.
  • Screen operations including screen capture and active window detection.
  • Clipboard integration for managing clipboard content.

Use cases of MCPControl?

  1. Automating repetitive tasks on your computer.
  2. Enabling AI models to interact with applications and games.
  3. Managing multiple windows and applications programmatically.

FAQ from MCPControl?

  • Is MCPControl safe to use?

This software is experimental and potentially dangerous. Use it at your own risk in controlled environments.

  • What platforms does MCPControl support?

MCPControl aims to support Windows, Linux, and macOS, though most testing has been on Windows.

  • How can I contribute to MCPControl?

Contributions are welcome! Please refer to the CONTRIBUTING.md file in the repository for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Cheffromspace
Star
78
Language
TypeScript
License
MIT 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