What it is

MokoWindows (@mokoconsulting/mcp-mokowindows) is an MCP server that gives an AI agent controlled, tool-level access to a Windows machine. Rather than handing the assistant a raw shell, it exposes 80+ purpose-built tools - each one a scoped operation such as "list running processes," "set the display resolution," "read a registry key," or "screenshot a specific window" - so actions stay predictable and auditable.

It is written in TypeScript, runs on Node.js, and keeps dependencies light: only the MCP SDK and the zod validation library. Notable capabilities include occlusion-tolerant single-window capture (windows_window_capture), which screenshots one application window through the Win32 PrintWindow API even when the window is minimized, hidden behind others, on a second monitor, or on another virtual desktop; and a dedicated, isolated Chrome automation tool (windows_chrome_control) built for testing web apps, complete with responsive/mobile viewport emulation and one-time Google OAuth sign-in.

Current version: 3.10.0. Licensed under GPL-3.0-or-later.

Install (npm)

MokoWindows is published to public npm under the @mokoconsulting scope. Install it globally:

npm install -g @mokoconsulting/mcp-mokowindows

Or run it on demand without a global install:

npx -y @mokoconsulting/mcp-mokowindows

Requires Node.js 20+ on Windows (it uses Win32 APIs and PowerShell). Google Chrome is only needed for the windows_chrome_control tool. Optionally, you can pull the package from the MokoGIT registry mirror by adding this scope-to-registry mapping to your .npmrc:

@mokoconsulting:registry=https://git.mokoenterprises.us/api/packages/MokoConsulting/npm/

Configure

Register the server with your MCP client. For Claude Code:

claude mcp add -s user mokowindows -- mcp-windows

Or add it to your MCP config (~/.claude.json or a project .mcp.json):

{
  "mcpServers": {
    "mokowindows": {
      "type": "stdio",
      "command": "mcp-windows"
    }
  }
}

Restart your MCP client so it loads the server at startup.

Server behavior is controlled by a config file at ~/.mcp_windows.json, managed through the windows_mcp_config tool. Key settings:

• chromeProfile - default Chrome profile (--profile-directory) for windows_chrome_control
• chromeUserDataDir - default Chrome profile store (--user-data-dir)
• blockedCommands - commands refused by windows_execute
• allowedDirectories - filesystem access allow-list
• outputLineLimit, commandTimeout - output and timeout limits

Tooling

MokoWindows exposes 80+ tools organized into these categories (source module names in parentheses):

• Core & shell - run commands, query system info, and drive persistent terminals: windows_execute, windows_system_info, windows_terminal_*.
• Files & storage - read/write/edit files, search, list drives, disk cleanup, recycle bin: windows_file_read/write/edit, windows_file_search, windows_drives, windows_storage, windows_recycle_bin.
• Processes & services - enumerate and control both: windows_process_list/kill, windows_service_list/control.
• Audio & display - output/input devices and per-app volume, monitors, theme: windows_audio_* (including per-app volumes), windows_display_get/set, windows_theme_*.
• Power & network - power actions, network info and connections, Wi-Fi, firewall, Bluetooth, hosts file, DNS: windows_power_*, windows_network_*, windows_wifi_*, windows_firewall_*, windows_bluetooth_*, windows_hosts_file.
• System administration - registry, environment variables, scheduled tasks, startup entries, installed apps, services, USB devices, certificates, notifications: windows_registry_*, windows_env_*, windows_task_scheduler_*, windows_startup_*, windows_installed_apps, windows_usb_devices.
• Packages & WSL - winget package management and WSL distro control: windows_winget_*, windows_wsl_*.
• Window capture - occlusion-tolerant single-window screenshots plus window listing/control and virtual desktops: windows_window_capture, windows_window_list/control, windows_virtual_desktop, windows_screen_capture.
• Chrome browser automation - launch and drive a dedicated, isolated Chrome over the DevTools Protocol for web-app testing: windows_chrome_control (navigate, click, type, run JS, screenshot; responsive/mobile viewport presets; selectable profiles; one-time Google OAuth login).
• Desktop utilities - clipboard, dialogs, notifications, focus mode, printers: windows_clipboard_get/set, windows_dialog, windows_notification_send, windows_printer_list.

See the Wiki for the full tool reference.

Get help

Need a hand getting MokoWindows installed or configured? Open a support ticket with MokoConsulting, or call (931) 820-0265.