Windows computer use in the background for Codex: UI Automation, Win32 messages, read back.
MCPpedia last refreshed this data
io.github.pironjulien/nexus-windows-codex is an MCP server that windows computer use in the background for Codex: UI Automation, Win32 messages, read back. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 83/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-pironjulien-nexus-windows-codex": {
"args": [
"-y",
"nexus-windows-codex"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Windows computer use in the background for Codex: UI Automation, Win32 messages, read back.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked nexus-windows-codex against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
MCP WordPress Remote proxy server
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
MCP Security Weekly
Get CVE alerts and security updates for io.github.pironjulien/nexus-windows-codex and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Windows computer use for Codex, in the background. An MCP server (nexus-windows-codex, one npx command) that
lets OpenAI Codex see and operate Windows desktop applications while the user keeps their mouse, keyboard and
foreground window. Codex's own Computer Use came to macOS first; on Windows, OpenAI's documentation says to keep the
target app visible on the active desktop while it runs (Codex docs).
NexusWindows for Codex has its own local .NET helper for everything: window inventory, UI Automation tree, PrintWindow
capture of covered windows, Win32 messages and UI Automation patterns without focus, and its own real mouse and
keyboard as the last resort, under a shared foreground token. Every action is judged from the application's real
state, and a batch needs an explicit postcondition per step. It also ships as a Codex skill that layers the same session over Codex's Computer Use API (@oai/sky).
Version 3.7.2 · Windows 10/11 · Node 22+ · .NET 10 · MIT licence
Part of the Nexus family: NexusWindows (Claude · Codex · Antigravity), NexusBrowser (repo), NexusAndroid (repo). Project page: julienpiron.fr/nexuswindows.
Codex's built-in Computer Use acts with the physical mouse and keyboard: it brings the target window to the front and the user has to stop working while it acts. Many Windows applications can be driven without that. NexusWindows for Codex tries the background techniques first, judges the result from the application's real state, and only uses its helper's real mouse and keyboard as a fallback, after a pause in the user's own typing and under a token shared with the other agents on the PC.
It is an MCP server (Node, no npm dependency) with a self-contained .NET helper: no listening network port, no token and no private Electron API. The optional Codex skill runs the same session in Codex's Node REPL instead, over Codex's