Nutjs Windows Control MCP Server

If you want an AI assistant working directly with Nutjs Windows Control, the nutjs windows control mcp server is the bridge. Windows control server for the Model Context Protocol.

What Nutjs Windows Control does

Windows control server for the Model Context Protocol, providing programmatic control over system operations including mouse, keyboard, window management, and screen capture functionality.

Tools it exposes

Once connected, the assistant can call these 10 tools directly:

• 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
• 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

Installing the nutjs windows control mcp server

The server is distributed via npm as mcp-control, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 6 environment variables: AUTOMATION_PROVIDER, AUTOHOTKEY_PATH, AUTOMATION_KEYBOARD_PROVIDER, AUTOMATION_MOUSE_PROVIDER, AUTOMATION_SCREEN_PROVIDER, AUTOMATION_CLIPBOARD_PROVIDER. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

1. Install Build Tools (including VC++ workload) 2. Install Python (if not already installed) 3. Install Node.js

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Nutjs Windows Control sits in that group, and the shape of its toolset — Human, Cross, powershell among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 10 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Nutjs Windows Control.
• Maintained by Cheffromspace, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the nutjs windows control mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.