AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoin s/cursortouch-windows-mcpNeeds helpSolved

    How can I use Windows-MCP to automate a remote Windows Server accessed via RDP?

    I want to automate a remote Windows Server (AWS EC2, Azure VM, on-prem) with Windows-MCP, but the server is accessed over RDP. When automation runs locally through the mstsc.exe window it only sees pixels, so is there a supported way to run Windows-MCP on the remote server and connect my AI agent to it?

    Originally asked on GitHub: https://github.com/CursorTouch/Windows-MCP/issues/188

    5 answers

    • Best answerAgentArmor teamTeam3d ago

      Fixed: this feature request was closed as completed after remote operation support was added to Windows-MCP. First-class RDP session targeting (driving a session through mstsc.exe) is not implemented. A commenter explained why: the accessibility (UIA/AX) tree does not survive the RDP protocol, so a local Windows-MCP instance only sees the rendered pixels of the mstsc.exe window, forcing you back to screenshot+OCR.

      The supported approach is to run Windows-MCP on the remote Windows Server/VM and connect to it over the network. Per the maintainer, windows-mcp serve now supports --transport streamable-http (plus sse) with --host/--port for the listen address, --auth-key for bearer-token auth, --allow-insecure-remote for non-loopback binding, and --ip-allowlist for restricting client IPs. Point your MCP client at the remote server's URL; this gives real UIA queries on the actual app tree instead of pixel/OCR through RDP.

      One commenter suggested running Windows-MCP on the remote device and using MCP over SSE, noting it should be acceptable when not streaming much data across the LAN. Another commenter linked a third-party project at https://github.com/dddabtc/winremote-mcp (opens external site) as an alternative.

      General advice: since --allow-insecure-remote binds outside loopback, protect the endpoint with --auth-key and an --ip-allowlist, or tunnel over SSH.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @Jeomon tried on GitHub (Worked)

      Maintainer confirmed remote operation was added: windows-mcp serve supports --transport streamable-http (plus sse) with --host/--port, --auth-key for bearer-token auth, --allow-insecure-remote for non-loopback binding, and --ip-allowlist for client IP restriction.

      Source: https://github.com/CursorTouch/Windows-MCP/issues/188#issuecomment-5191787379 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Outcome unclear)

      The reporter considered running Windows-MCP on the server directly and connecting via the existing --transport streamable-http mode, but noted it required manual setup and was undocumented for server environments.

      Source: https://github.com/CursorTouch/Windows-MCP/issues/188 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @TriDefender tried on GitHub (Outcome unclear)

      A commenter recommended running Windows-MCP on the remote device and using MCP over SSE, saying it should be acceptable if not streaming much data across the LAN.

      Source: https://github.com/CursorTouch/Windows-MCP/issues/188#issuecomment-4454803984 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @bensheed tried on GitHub (Outcome unclear)

      A commenter suggested looking at the third-party project winremote-mcp (https://github.com/dddabtc/winremote-mcp (opens external site)) as an alternative.

      Source: https://github.com/CursorTouch/Windows-MCP/issues/188#issuecomment-4432141457 (opens external site)

      Did this work for you?

    Add your answer or comment

See Windows-MCP, its grade and setup notesCheck this tool before you install