claude-did-this/MCPControl

Windows control server for the Model Context Protocol, providing programmatic control over system operations including mouse, keyboard, window management, and screen capture functionality.
> **Note**: This project currently supports Windows only.
🔥 Why MCPControl?
MCPControl bridges the gap between AI models and your desktop, enabling secure, programmatic control of:
- 🖱️ **Mouse movements and clicks**
- ⌨️ **Keyboard input and shortcuts**
- 🪟 **Window management**
- 📸 **Screen capture and analysis**
- 📋 **Clipboard operations**
🔌 Quick Start
Prerequisites
1. **Install Build Tools (including VC++ workload)**
2. **Install Python** (if not already installed)
3. **Install Node.js**
Installation
1. **Install MCPControl Package**
Configuration
MCPControl works best in a **virtual machine at 1280x720 resolution** for optimal click accuracy.
Configure your Claude client to connect to MCPControl via SSE transport:
Option 1: Direct SSE Connection
For connecting to an MCPControl server running on a VM or remote machine:
Replace 192.168.1.100:3232 with your server's IP address and port.
Option 2: Local Launch with SSE
To launch MCPControl locally with SSE transport:
Starting the Server
First, start the MCPControl server on your VM or local machine:
The server will display:
- Available network interfaces and their IP addresses
- The port number (default: 3232)
- Connection status messages
VM Setup Example
1. **Start your Windows VM** with 1280x720 resolution
2. **Install MCPControl** on the VM:
3. **Run the server** with SSE transport:
4. **Note the VM's IP address** (e.g., 192.168.1.100)
5. **Configure Claude** with the SSE URL:
6. **Restart Claude** and MCPControl will appear in your MCP menu!
🔧 CLI Options
MCPControl supports several command-line flags for advanced configurations:
Command Line Arguments
- --sse - Enable SSE (Server-Sent Events) transport for network access
- --port [number] - Specify custom port (default: 3232)
- --https - Enable HTTPS/TLS (required for remote deployments per MCP spec)
- --cert [path] - Path to TLS certificate file (required with --https)
- --key [path] - Path to TLS private key file (required with --https)
Security Note
According to the MCP specification, HTTPS is **mandatory** for all HTTP-based transports in production environments. When deploying MCPControl for remote access, always use the --https flag with valid TLS certificates.
🚀 Popular Use Cases
Assisted Automation
- **Application Testing**: Delegate repetitive UI testing to Claude, allowing AI to navigate through applications and report issues
- **Workflow Automation**: Have Claude operate applications on your behalf, handling repetitive tasks while you focus on creative work
- **Form Filling**: Let Claude handle data entry tasks with your supervision
AI Experimentation
- **AI Gaming**: Watch Claude learn to play simple games through visual feedback
- **Visual Reasoning**: Test Claude's ability to navigate visual interfaces and solve visual puzzles
- **Human-AI Collaboration**: Explore new interaction paradigms where Claude can see your screen and help with complex tasks
Development and Testing
- **Cross-Application Integration**: Bridge applications that don't normally communicate
- **UI Testing Framework**: Create robust testing scenarios with visual validation
- **Demo Creation**: Automate the creation of product demonstrations
⚠️ IMPORTANT DISCLAIMER