Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Computer or cloud✓ browser-use.com
Personae
Overview
Description from the maker (original English)
Control specific, already-open account-isolated Personae browser identities with MCP.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 39/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Web & browsers
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"personae": {
"command": "npx",
"args": [
"-y",
"@leek-emperor/personae-mcp"
]
}
}
}Run this in your terminal
claude mcp add personae -- npx -y @leek-emperor/personae-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"personae": {
"command": "npx",
"args": [
"-y",
"@leek-emperor/personae-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"personae": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@leek-emperor/personae-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account leek-emperor, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Web & browsersi
- More stars than 0% of the other 1394 servers in this category
- Published to the registry more recently than 30% of the other 1394 servers in this category
- Basic checks equal to or better than 100% of the other 1394 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Personae safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Chrome DevTools MCP
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Personae
A multi-identity browser · every identity is an isolated partition, every window is agent-controllable
Bundles agent-browser and an MCP server — no Node or CLI install needed
English · 中文
An Electron desktop browser that combines two things: multi-account isolation and letting AI agents drive the browser.
- Each browser identity is its own Chromium
persist:partition — cookies, localStorage and login state are fully isolated, so you can be signed into the same site under several accounts at once. - Each identity is a standalone window with back/forward buttons and an address bar. It behaves like an ordinary browser.
- The agent-browser binary is bundled, and those windows are exposed over MCP, so Codex / Claude Code can drive the page of a specific identity.
Users don't need to pre-install Node, Chrome for Testing, or any CLI.
MCP Registry
Personae is published to the official MCP Registry as io.github.leek-emperor/personae after its first Registry-enabled release. The Registry package is a small stdio launcher for a running, separately installed Personae desktop app — it does not replace the browser application or create a cloud browser.
After installing and launching Personae, a client that supports npm MCP packages can run:
npx -y @leek-emperor/personae-mcpThe launcher discovers Personae through its local bridge and keeps each tool call scoped to the identity named in the request. It uses no API key and opens no public network listener. The app's Configure Codex control remains the recommended setup path because it uses the bundled Electron runtime and needs no Node installation.
The problem it solves
Existing browser-automation tools assume the agent launches the browser. If your product _is_ a browser client, it's the other way around: the windows already exist, and they belong to different account identities. What the agent needs is to attach without crossing identities.
The approach here:
- The app opens a CDP port on startup (system-assigned, loopback only).
- When an identity window opens, the main process resolves the authoritative targetId of its content page via
Target.getTargetInfo. - A local bridge exposes the
identity → targetIdmapping. - The MCP server uses that targetId directly as a tab ref — a single-step hit.
So snapshot(identity: "Account A") and snapshot(identity: "Account B") always land on the right window, even when both have the same site open with identical titles and URLs.
Quick start
Requires Node ≥ 20 and pnpm (for development only; the packaged app depends on neither).
agent-browser must be ≥ 0.36. Below that, tab list --json does not emit targetId, which is the only thing tying an identity to its window — every tool would fail to find its target. The version in package.json is already pinned; don't downgrade it.
pnpm installpnpm bundle:ab # copy the agent-browser binary and core skill into resources/ pnpm dev
Add one or two browser identities in the UI, then click an identity to open its window.
The interface is in English by default. Use the EN / 中 toggle in the top-right corner to switch to Chinese; the choice is remembered and also applies to the toolbar inside each identity window and to the agent prompt you copy out.
Tests
The tricky, mostly-undocumented decisions live in small pure modules so they can be locked down by tests. They run on node:test with no extra dependencies:
pnpm testCovered: the window.open / popup decision (window-open.ts), the proxy input parsing (proxy.ts), address-bar URL normalization (url-input.ts), the Codex-config TOML splice (toml.ts), and the identity palette (colors.ts).
Packaging:
pnpm build:mac # or build:winThe default is adhoc signing (identity: '-'), which needs no Apple Developer certificate and runs fine on the build machine. But an adhoc-signed app cannot be distributed — Gatekeeper will block it on someone else's Mac. For real distribution, supply a certificate via environment variables and set notarize to true:
CSC_LINK=/path/to/cert.p12 CSC_KEY_PASSWORD=... \APPLE_ID=... APPLE_APP_SPECIFIC_PASSWORD=... APPLE_TEAM_ID=... \ pnpm build:mac
Connecting Codex / Claude Code
The fastest path: let the agent connect itself
The UI has a "Let the agent connect itself" block that renders a ready-to-send prompt. Copy it, paste it into Codex or Claude Code, and the agent will write its own MCP config, restart, and verify the link by calling list_identities.
The prompt isn't just a config snippet — it also tells the agent what the 13 tools do and which mistakes to avoid (stale refs, guessing at agent-browser syntax, trying to tell identities apart by page title). It's generated from live runtime values, so the paths in it are always correct for the machine it's running on.
Or click one button
The same panel has a one-click install that writes the MCP server into ~/.codex/config.toml (idempotent, with an automatic backup first). Paths are resolved at runtime from process.execPath, so they can't be wrong.
Or configure it by hand
On macOS:
[mcp_servers.personae]command = "/Applications/Personae.app/Contents/MacOS/Personae" args = ["/Applications/Personae.app/Contents/Resources/mcp-server.mjs"]
[mcp_servers.personae.env] ELECTRON_RUN_AS_NODE = "1"
The executable under Contents/MacOS/ follows productName, so it's Personae. Note that electron-builder's executableName only applies to Windows.
command points at the app's own binary; ELECTRON_RUN_AS_NODE=1 makes it degrade into a plain Node runtime. That's why no Node install is required (verified: with PATH set to /usr/bin:/bin, the full flow still works).
Claude Code:
claude mcp add personae \--env ELECTRON_RUN_AS_NODE=1 \ -- /Applications/Personae.app/Contents/MacOS/Personae \ /Applications/Personae.app/Contents/Resources/mcp-server.mjs
MCP tools
Every tool takes an identity argument (name or id).
| Tool | Purpose |
|---|---|
load_skill | Fetch the real command syntax of the bundled agent-browser version (returns a section index by default; pass section for a specific one) |
list_identities | List all identities with open state and current URL |
open_identity | Open an identity's window |
snapshot | Accessibility-tree snapshot returning [ref=eN] element refs |
navigate | Navigate to a URL |
click / fill / press | Interaction; click accepts either a ref or visible text |
act | Run several commands inside one agent-browser process |
get_text / get_url | Read content |
screenshot | Capture a screenshot |
eval_js | Evaluate JavaScript |
When click / fill receive an @eN ref they automatically take a snapshot first, because refs are only valid within a single agent-browser process — reusing one across processes always fails with Unknown ref. For multi-step interactions, put them in one act batch.
Driving a popup child window. When a page opens a popup (an OAuth sign-in, a share dialog…), that popup becomes a child window belonging to the same identity (see Popups and OAuth). It's a separate CDP target, listed under the identity in list_identities as children. Every acting/reading tool takes an optional target argument — pass a child's targetId (or its index) to drive the popup instead of the main window; omit it to drive the main window as before.
Architecture
┌─────────────────────────────────────────────────────────┐│ Electron main process │ │ │ │ ├─ CDP server (port 0 → system-assigned, 127.0.0.1 only)│ │ ├─ IdentityManager storage / window lifecycle / target │ │ └─ Agent Bridge local HTTP, exposes identity↔target │ └───────────┬─────────────────────────────────┬────────────┘ │ │ ┌─────────▼──────────┐ ┌───────────▼───────────┐ │ Identity window │ │ Discovery file │ │ (one per identity) │ │ userData/ │ │ │ │ agent-bridge.json │ │ BrowserWindow shell│ │ (port changes every │ │ ├ WebContentsView │ │ launch; found via │ │ │ chrome.html │ │ a fixed path) │ │ └ WebContentsView │ └───────────┬───────────┘ │ content │ │ │ ↑ agent acts │ │ └────────────────────┘ │ │ ┌─────────────────────────────────▼───────────┐ │ scripts/mcp-server.mjs (stdio JSON-RPC) │ │ read discovery → get targetId → run CLI │ └───────────────────┬─────────────────────────┘ │ ┌───────────▼────────────┐ │ Codex / Claude Code │ └────────────────────────┘
Why each identity window is "a shell plus two WebContentsViews"
The goal is to wrap third-party pages in our own navigation UI without using the tag. So:
- the shell
BrowserWindowis only a container and loadsabout:blank; - the top bar is a local
chrome.htmlwith a dedicated preload exposing just six navigation methods; - the content area is a
WebContentsViewwhere the partition applies, and it deliberately loads no preload at all, keeping third-party pages untouched.
Nested BrowserWindows and BrowserView both work too, and the agent can drive all three (all verified). WebContentsView was chosen because BrowserView is marked @deprecated in Electron's type definitions, and because a nested window is a separate native window on macOS — dragging, resizing and minimizing would
Only the beginning is shown; read the rest in the repo