Yab, Yet Another Browser vs Chrome MCP Secure
A side-by-side look at the Yab, Yet Another Browser and Chrome MCP Secure MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Yab, Yet Another Browser for browser automation work as a local process; choose Chrome MCP Secure for browser automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Yab, Yet Another Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
devtools_comments, devtools_console, devtools_network.
Choose Chrome MCP Secure when
- You need dedicated capabilities in the Browser Automation domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
COMPLIANCE_LOG_FORMAT, COMPLIANCE_LOG_DIR, SYSLOG_HOST, SYSLOG_PORT. - You want tools like
health, navigate, get_tabs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 56/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | COMPLIANCE_LOG_FORMATCOMPLIANCE_LOG_DIRSYSLOG_HOSTSYSLOG_PORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 8 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 69 | 22 |
| Full listing | View Yab, Yet Another Browser | View Chrome MCP Secure |
Tools & capabilities
Yab, Yet Another Browser tools 69
devtools_commentsRead user-authored comments on elements of an already inspected, non-private tab.devtools_consoleRead recorded Console messages from an already inspected, non-private tab.devtools_networkRead sanitized request metadata recorded by the tab's Developer Tools.devtools_traceRead the WebKit Performance recording's event names, durations and nesting.devtools_stylesRead the currently selected element's matched and computed styles from Developer Tools.native_contextRead Yab's own current settings, spaces, tabs, mail accounts, permissions and this task's native operations.native_actionsList native Yab actions with their strict argument schemas, targetKind, undo support and permission requirements.native_applyPerform a native Yab action explicitly requested by the user: settings, spaces, tabs, page fonts or connecting Gmail.native_operationRead this task's native operation by operationId, or wait for a change up to seconds (0 to 10).native_undoUndo a native change of this task by its changeId (or the last undoable change).tabsList the tabs open in Yab, the user's web browser: the user's and the agents'.openOpen a web page (URL) in a new agent tab in Yab, the user's browser, signed in to their sites, beside the user's tabs.- +57 more on the listing page
Chrome MCP Secure tools 22
healthCheck Chrome connection and versionnavigateNavigate to URLget_tabsList all Chrome tabsclick_elementClick element by CSS selectorclickClick at coordinatestypeType text at cursorget_textExtract text from elementget_page_infoGet URL, title, interactive elementsget_page_stateGet scroll position, viewport sizescrollScroll to coordinatesscreenshotCapture page screenshotwait_for_elementWait for element to appear- +10 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.
Yab, Yet Another Browser
{
"mcpServers": {
"yab-yet-another-browser": {
"command": "npx",
"args": [
"-y",
"yab-mcp"
]
}
}
}
Chrome MCP Secure
No confirmed install command for Chrome MCP Secure yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Yab, Yet Another Browser is categorized under Browser Automation and uses a local stdio subprocess. Chrome MCP Secure belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Yab, Yet Another Browser for browser automation work and Chrome MCP Secure 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. Chrome MCP Secure has no confirmed install command yet — follow its own setup instructions.
Yab, Yet Another Browser has no declared pricing — check the project's own site. Chrome MCP Secure is listed as free. Auth: api key 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 yab-yet-another-browser and pantheon-security-chrome-mcp-secure as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Yab, Yet Another Browser has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Chrome MCP Secure has 48/100 (Fair) with 3 views, 0 installs and 8 GitHub stars.