MouseMux hosts a local MCP server. Connect your AI, arm it, and it gets its own cursor to click and type in any Windows app, no API required. One agent can drive many apps at once, each through its own locked virtual user.
In beta. The MCP server is local-only (127.0.0.1), off by default, and gated behind an Arm switch.
The Input Mapper turns MouseMux input into a live signal graph. MCP hands that graph to your AI, and an Arm switch decides when it can act.
The Input Mapper is a visual node graph inside MouseMux. Every device that connects becomes a live signal source, mouse, keyboard, pen and touch, that you wire through processing nodes and out to real or virtual users.
Three signal types flow through it: vector positions, scalar values like pressure and wheel, and binary key and button events. Over 130 nodes cover math, filters, gates, generators, coordinate transforms, screen reading with OCR and image match, and automation macros.
That makes it a genuinely powerful toolkit: any input can be routed to become any output, and you can spin up unlimited virtual users - driving normal Windows apps, isolated multi-seat browsers, and soon any app fully sealed in its own container.
The app hosts a local Model Context Protocol server, so any MCP-compliant AI can connect: Claude Desktop and Claude Code work out of the box, and so does any other assistant, coding agent or agent framework that speaks MCP. The AI reads the whole graph, builds and rewires nodes, and creates virtual users on the machine - as many as the task needs, one per app, each locked to its own window so parallel work stays isolated and no human's pointer is ever touched.
Reading and building is always safe. Acting, moving, clicking and typing, is gated behind an Arm switch that is off by default and turns red while live, and the server listens on 127.0.0.1 only. Inside the graph, an LLM node can call Claude, OpenAI or your own API when a step needs judgement.
Get the Input Mapper app, connect your AI, and arm it when you're ready.