NexusWindows for Claude

io.github.pironjulienPublished by GitHub account pironjulienv3.7.4Updated Nov 6, 2026

Windows computer use in the background: UI Automation and Win32 messages, every action read back.

The publisher's own server: Claude Platform Docs

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

Lets an assistant drive Windows desktop apps in the background via UI Automation and Win32 messages, reading back every action it performs.

What you can do
  • Control Windows desktop applications in the background using UI Automation and Win32 messages.
  • Perform UI actions on windows and controls without bringing them to the foreground.
  • Read back the result of each action to verify what actually happened.
  • No tool list is published, so the exact set of actions is not documented in the supplied material.
When to use it
Useful when an assistant needs to operate Windows desktop programs on the user's own machine, especially when the target window should stay in the background rather than take focus.
Requirements
Runs locally as a stdio process on Windows, launched with uvx from the PyPI package, so a Python/uv environment is needed. Desktop only; no web executable. Setting PYTHONUTF8 is recommended for UTF-8 mode on Windows. No authentication is declared.
Before you install
It acts on real desktop applications, so actions can change or delete data in those programs; the read-back is the main safeguard. It is Windows-only and desktop-only. No tool list or README is provided, so review what it can do before granting access.

Installation

In SourceWeft

  1. Open NexusWindows for Claude in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package did not install.

Version history

5
  1. v3.7.4LatestOct 29, 2026
  2. v3.3.1Oct 26, 2026
  3. v3.3.0Oct 26, 2026
  4. v3.1.4Oct 24, 2026
  5. v3.0.1Oct 23, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

Other Claude integrations