Browserctl MCP vs Browser Controller
A side-by-side look at the Browserctl MCP and Browser Controller MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
Browser ControllerBrowser Automation · Local subprocess (stdio)MCP server + Chrome extension that gives AI agents control of your real browser with existing sessions and logins59GoodAuth: no auth requiredVerdict: choose Browserctl MCP for browser automation work as a local process; choose Browser Controller for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Browserctl MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
browser_status, browser_start, browser_stop.
BChoose Browser Controller when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
browser_navigate, browser_tabs, browser_snapshot.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Browser Controller | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 57/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 7 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 25 | 17 |
| Full listing | View Browserctl MCP | View Browser Controller |
Tools & capabilities
Browserctl MCP tools 25
browser_statusbrowser_startbrowser_stopbrowser_navigatebrowser_tabsbrowser_snapshotbrowser_read_pagebrowser_findbrowser_extractbrowser_get_contentbrowser_get_propertybrowser_click- +13 more on the listing page
Browser Controller tools 17
browser_navigate- `url` (required): an address (scheme optional: `https://` is added; `http://` for `localhost`, `127.0.0.1` and `[::1]`), or `back`, `forward`, `reload`.browser_tabs- `action`: `list` (default), `close` or `focus`. `close` and `focus` need `tabId`.browser_snapshot- `tabId` (required).browser_text- `tabId` (required); `target` (the element); `maxChars` (20000; 100–100000).browser_screenshot- `tabId` (required); `target` (crop to the element's box); `region` (`{x, y, width, height}` in CSS px, crop to a rectangle).browser_inspect_element- `tabId`, `target` (required).browser_click- `tabId`, `target` (required; a point `x,y` is allowed).browser_type- `tabId` (required); `target`; `text`; `key`; `clear` (false); `submit` (false). Give at least one of `text`, `key`, `clear` or `submit`.browser_fill- `tabId` (required); `fields` (1–50 entries of `{target, value}`; `value` is a string, a number, a boolean or an array of strings).browser_scroll- `tabId` (required); `target`; `dy` and `dx` (pixels).browser_wait- `tabId` (required); exactly one of `target`, `url` or `ms`; `gone` (false; with `target`); `timeout` (10000; 1–50000).browser_evaluate- `tabId`, `expression` (required); `timeout` (5000; 1000–30000).- +5 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Browserctl MCP
{
"mcpServers": {
"browserctl-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"browserctl-mcp",
"browserctl-mcp"
]
}
}
}
Browser Controller
{
"mcpServers": {
"browser-controller": {
"command": "npx",
"args": [
"-y",
"browser-controller"
]
}
}
}
Frequently asked questions
Browserctl MCP is categorized under Browser Automation and uses a local stdio subprocess. Browser Controller belongs to Browser Automation and uses a local stdio subprocess. Pick Browserctl MCP for browser automation work and Browser Controller for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Browserctl MCP is listed as free. Auth: no auth required. Browser Controller is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add browserctl-mcp and browser-controller as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browserctl MCP has a quality signal of 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Browser Controller has 59/100 (Good) with 0 views, 0 installs and 7 GitHub stars.
