Uindow

What is Uindow?

Uindow drives a real, signed Chromium/Electron browser with genuine OS-level input—actual cursor movement, real keystrokes, and native file dialogs—running entirely on your own machine and network. It provides an MCP server so AI agents can create and control web-automation agents that are immune to prompt injections.

How to use Uindow?

Launch the MCP server with npx -y @uindow/cli mcp and configure your MCP‑compatible client (Claude Desktop, Cursor, VS Code, etc.) to use that stdio command. Alternatively, use the integrated no‑code recorder or write automations in pure JavaScript inside the built‑in IDE.

Key features of Uindow

• Real Chromium browser with genuine OS‑level input
• Immune to prompt injections
• MCP server for AI agent control
• No‑code recorder for automation without programming
• Full CLI for managing agents and app lifecycle
• Runs completely locally on your machine

Use cases of Uindow

• Control browser automation from Claude or Cursor via MCP
• Record and replay web workflows without coding
• Automate CI/CD browser testing pipelines
• Write custom browser scripts using the integrated IDE

FAQ from Uindow

What makes Uindow immune to prompt injections?

It uses genuine OS‑level input (actual cursor movement, real keystrokes) rather than synthetic page events, so injected JavaScript in web pages cannot affect the automation.

How do I run the MCP server?

Run npx -y @uindow/cli mcp in your terminal. Then configure your MCP client (Claude Desktop, Cursor, VS Code, etc.) with the same command as shown in the README.

What are the system requirements?

Uindow runs on your own machine. The npx command fetches the signed Electron binary if not present, or you can use prebuilt binaries for macOS, Windows, and Linux from the Releases page. A free Uindow account