1. Home
  2. Windows-MCP
  3. Windows-MCP for Cursor: Setup & Config

Data as of

Windows-MCP for Cursor: Setup & Config

Cursor: Let an AI assistant interact with Windows applications, windows, and input controls.

What you can do with Windows-MCP in Cursor

Choose native Windows automation with optional DOM inspection and documented remote-access controls.

  • Inspect web page content using the browser DOM mode.
  • Expose selected desktop tools to a secured network client.

Before you start: Windows-MCP in Cursor

  • Windows
  • Python 3.13+
  • uv with uvx
  • An MCP-compatible client

This is the documented default stdio launch. English is preferred for App-Tool; disable that tool for other Windows languages. For network access, configure authentication and TLS rather than using an unprotected listener.

Windows-MCP Cursor configuration

  1. Choose Cursor configuration scope

    For Windows-MCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add Windows-MCP to Cursor

    Use the Windows-MCP entry below in mcpServers. Keep Windows-MCP's documented stdio connection fields and your other Cursor entries.

  3. Check Windows-MCP in Cursor

    Windows-MCP: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "Windows-MCP": {
      "command": "uvx",
      "args": [
        "windows-mcp",
        "serve"
      ],
      "env": {}
    }
  }
}

Windows-MCP tools available to Cursor

Windows-MCP's stored tool list documents 5 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

Screenshot

Find Screenshot under Windows-MCP in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Capture screen imagery; this tool name appears in the README's tool-selection example.

Click

Find Click under Windows-MCP in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Snapshot

Find Snapshot under Windows-MCP in Cursor's MCP settings; inspect its arguments when the agent requests a call.

PowerShell

Find PowerShell under Windows-MCP in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Expose PowerShell capability, which the README demonstrates excluding from the enabled tool set.

Registry

Find Registry under Windows-MCP in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Expose Windows Registry capability, which the README demonstrates excluding from the enabled tool set.

Windows-MCP: full stored tool descriptions

Troubleshooting Windows-MCP in Cursor

  • Cursor must find uvx windows-mcp (from uv, for Python tools) for Windows-MCP. Enable the project/user entry in MCP settings and inspect its tools.
  • Windows-MCP uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires Windows-side execution even when the assistant runs in WSL.
  • Known limitation: Python 3.13+ is required by the documented setup.
  • Known limitation: Non-English Windows setups may need the application tool disabled.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

Windows-MCP — details. Cursor guide

Frequently asked questions

Cursor's Windows-MCP entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's Windows-MCP example uses stdio.

Windows-MCP's Cursor configuration invokes uvx windows-mcp (from uv, for Python tools).

Windows-MCP's stored list contains 5 tools, including Screenshot, Click, Snapshot. Compare those names with Cursor's connected tool list; the stored list is not a live check.

Yes. --tools selects an allowlist and --exclude-tools disables named capabilities; the README illustrates excluding PowerShell and Registry.

Yes. The documented install command creates a per-user scheduled task, and an uninstall command removes it.