Windows control server for the Model Context Protocol
MCPControl MCP server exists for a simple reason — assistants are far more useful when they can act on MCPControl directly instead of describing what you should do. Windows control server for the Model Context Protocol.
Windows control server for the Model Context Protocol, providing programmatic control over system operations including mouse, keyboard, window management, and screen capture functionality.
Once MCPControl is connected, these are the calls the assistant has available:
Human — AI Collaboration**: Explore new interaction paradigms where Claude can see your screen and help with complex tasksCross — Application Integration**: Bridge applications that don't normally communicatepowershell — Windows PowerShell-based automation for simpler operationsautohotkey — AutoHotkey v2 scripting for advanced automation needsnode-gyp — npm install -g node-gypcmake-js — npm install -g cmake-jsindex.ts — Main application entry pointPrerequisites — 1. Install Build Tools (including VC++ workload) powershell # Run as Administrator - may take a few minutes to complete winget installInstallation — 1. Install MCPControl Package powershell npm install -g mcp-controlConfiguration — MCPControl works best in a virtual machine at 1280x720 resolution for optimal click accuracymcp-control on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 6 environment variables: AUTOMATION_PROVIDER, AUTOHOTKEY_PATH, AUTOMATION_KEYBOARD_PROVIDER, AUTOMATION_MOUSE_PROVIDER, AUTOMATION_SCREEN_PROVIDER, AUTOMATION_CLIPBOARD_PROVIDER. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCPControl's toolset — Human, Cross, powershell and 7 more — is a fair guide to whether it matches your workflow. It is maintained by Cheffromspace; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Human | AI Collaboration**: Explore new interaction paradigms where Claude can see your screen and help with complex tasks |
| Cross | Application Integration**: Bridge applications that don't normally communicate |
| powershell | Windows PowerShell-based automation for simpler operations |
| autohotkey | AutoHotkey v2 scripting for advanced automation needs |
| node-gyp | npm install -g node-gyp |
| cmake-js | npm install -g cmake-js |
| index.ts | Main application entry point |
| Prerequisites | 1. **Install Build Tools (including VC++ workload)** powershell # Run as Administrator - may take a few minutes to complete winget install Microsoft.VisualStudio.2022.BuildTools --override "--wait --passive --add Microso |
| Installation | 1. **Install MCPControl Package** powershell npm install -g mcp-control |
| Configuration | MCPControl works best in a **virtual machine at 1280x720 resolution** for optimal click accuracy. |
{
"mcpServers": {
"mcpcontrol": {
"command": "npx",
"args": ["-y", "mcp-control"],
"env": {
"AUTOMATION_PROVIDER": "your-value",
"AUTOHOTKEY_PATH": "your-value",
"AUTOMATION_KEYBOARD_PROVIDER": "your-value",
"AUTOMATION_MOUSE_PROVIDER": "your-value",
"AUTOMATION_SCREEN_PROVIDER": "your-value",
"AUTOMATION_CLIPBOARD_PROVIDER": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| AUTOMATION_PROVIDER | Configuration value read at startup. | Optional |
| AUTOHOTKEY_PATH | Credential the server authenticates with. | Yes |
| AUTOMATION_KEYBOARD_PROVIDER | Credential the server authenticates with. | Yes |
| AUTOMATION_MOUSE_PROVIDER | Configuration value read at startup. | Optional |
| AUTOMATION_SCREEN_PROVIDER | Configuration value read at startup. | Optional |
| AUTOMATION_CLIPBOARD_PROVIDER | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.