Uindow MCP server
io.github.uindow/uindow·v0.1.12·7 starsReal signed-browser automation for AI agents, over a local stdio MCP server.
7 stars88 downloads/wk
Reviews
Write oneNobody has reviewed Uindow yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Uindow tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 22 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Uindow compares
Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 85% of 866 Scraping and browsing servers
- GitHub stars
- 7
- more than 77% of 583 Scraping and browsing servers
- Downloads a week
- 88
- more than 52% of 309 Scraping and browsing servers with a package
Install Uindow in Claude Code, Cursor or VS Code
Runs npx -y @uindow/cli on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add uindow -- npx -y @uindow/cli
What the publisher says
From the Uindow repository's README, as published. We do not edit it. Read it on GitHub
Uindow - AI browser immune to prompt injections
Uindow drives a real, signed Chromium/Electron browser with genuine OS-level input - actual cursor movement, real keystrokes, and native file dialogs rather than synthetic page events. It runs entirely on your own machine and your own network, and every line of code it executes sits in plain sight in this repository.
Automate it three ways:
MCP server, so Claude, Cursor, VS Code, or any MCP-compatible client can list, create, and run automation modules directly. See Control Uindow from AI assistants.
- No code - build automations in the integrated editor and record complex workflows without writing code.
- From any AI assistants - Uindow ships a local
debug automations with ease. Auto-completion, code healing, JavaScript parsing, and linting are all built in.
- Write automations in pure JavaScript - Use the integrated development environment to write, test, and
Running Uindow
In order to use the app, create an account for free at uindow.com and follow the on-screen instructions.
Option 1 - Prebuilt binaries (recommended)
We build signed binaries for macOS, Windows, and Linux directly from the dist source, and host them on the GitHub Releases page (current and older versions) and on the Uindow install page.
Option 2 - npx
One command to fetch the CLI and launch the app:
npx -y @uindow/cli@latest app:startOther lifecycle commands:
npx @uindow/cli app:status # check whether the app is running
npx @uindow/cli app:stop # stop the appOption 3 - Run from source
Clone the repository and launch the app directly from source.
git clone https://github.com/uindow/uindow.git uindow
cd ./uindow/
npm install
npm startControl Uindow from AI assistents (MCP)
Uindow exposes a local Model Context Protocol server, so any MCP-compatible client can drive web-automation agents directly. The server communicates over stdio securely and is launched on demand by the AI assistant.
Requirements: Node.js 18+ with npx on your PATH.
npx -y @uindow/cli@latest mcpQuick reference
Uindow provides a 1-click connector for the most popular AI assistants.
Go to Uindow > AI assistants > Connect
JetBrains AI Assistant
Go to Settings > Tools > AI Assistant > Model Context Protocol (MCP) and click Add, then paste the JSON. In the same dialog, set the scope to Global rather than project-scoped so the server is available in every project you open, then click Apply to start it.
{
"mcpServers": {
"uindow": {
"command": "npx",
"args": ["-y", "@uindow/cli@latest", "mcp"]
}
}
}Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Uindow: common questions
- Is Uindow MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Uindow safety report
- How do I install Uindow?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Uindow need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Uindow maintained?
- The last commit was 53 days ago (2026-09-12). The latest release is v0.1.12.
- What can I use instead of Uindow?
- Servers from other publishers that do the same job: FableCut MCP server, Browsentic MCP server and Public Browser MCP server. Compare all Uindow alternatives.
- How does Uindow compare with other Scraping and browsing MCP servers?
- safety score 92/100 (higher than 85% of 866 Scraping and browsing servers); github stars 7 (more than 77% of 583 Scraping and browsing servers); downloads a week 88 (more than 52% of 309 Scraping and browsing servers with a package). Full comparison.
Alternatives to Uindow
Same job from other publishers: the closest match first, then the best rated.
- FableCutZero-dependency browser video editor AI agents drive via a JSON timeline over MCP; ffmpeg export.not reviewedEstablishedA
BrowsenticAgentic browser harness: your agent CLI in your real, signed-in browser, from a side panel or MCP.not reviewedEstablishedA
Public BrowserChrome over CDP for AI agents. Blind benchmark vs agent-browser: -33% tokens, -33% cost, -32% timenot reviewedGrowingA- CdpilotZero-dependency browser automation over raw CDP — no Puppeteer, Playwright, or Selenium.not reviewedGrowingB
WebReaperAI-native web scraper: scrape, crawl and map any site to clean markdown over stdio. MIT-licensed.not reviewedGrowingA