Agent Webbridge vs Oya Browser
A side-by-side look at the Agent Webbridge and Oya Browser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Webbridge for browser automation work as a local process; choose Oya Browser 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 Agent Webbridge when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
navigate, find_tab, evaluate.
Choose Oya Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OYA_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 59/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | OYA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12 | 354 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 15 | Not listed |
| Full listing | View Agent Webbridge | View Oya Browser |
Tools & capabilities
Agent Webbridge tools 15
navigateOpen a URL in a new or existing tabfind_tabLocate a tab by URL / titleevaluateRun JavaScript in the page, return the resultsnapshotAccessibility tree with stable `@e` element refsclickClick an element by `@e` ref (synthetic DOM click)trusted_clickReal mouse click (CDP, `isTrusted`) for pages that ignore `clickfillSet native inputs **and** `contenteditable` rich text fieldsuploadProgrammatically assign files to `<input type="file">file_chooser_interceptSuppress native OS file picker dialogs (Finder/Explorer) during programmatic uploadscreenshotCapture full-page or element screenshot directly to disksave_as_pdfSave the page as a PDFnetworkCapture network requests (`start`, `stop`, `list`, `detail`)- +3 more on the listing page
Oya Browser tools
No tool names declared yet. Check the project README from 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.
Agent Webbridge
{
"mcpServers": {
"agent-webbridge": {
"command": "npx",
"args": [
"-y",
"agent-webbridge"
]
}
}
}
Oya Browser
{
"mcpServers": {
"oya-browser": {
"command": "npx",
"args": [
"-y",
"@oya-ai/cli"
],
"env": {
"OYA_API_KEY": "YOUR_OYA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Agent Webbridge is categorized under Browser Automation and uses a local stdio subprocess. Oya Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Agent Webbridge for browser automation work and Oya Browser 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.
Agent Webbridge has no declared pricing — check the project's own site. Oya Browser has no declared pricing — check the project's own site. 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 agent-webbridge and oya-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Webbridge has a quality signal of 59/100 (Good) with 1 views, 0 installs and 12 GitHub stars. Oya Browser has 52/100 (Good) with 2 views, 0 installs and 354 GitHub stars.
