Openbrowser AI vs Oya Browser
A side-by-side look at the Openbrowser AI 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 Openbrowser AI 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 Openbrowser AI when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, GROQ_API_KEY, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_DEFAULT_REGION, AZURE_OPENAI_API_KEY.
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 | 47/100 · Fair | 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 | GOOGLE_API_KEYOPENAI_API_KEYANTHROPIC_API_KEYGROQ_API_KEYAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_DEFAULT_REGIONAZURE_OPENAI_API_KEY | OYA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 277 | 354 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Openbrowser AI | View Oya Browser |
Tools & capabilities
Openbrowser AI tools
No tool names declared yet. Check the project README from 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.
Openbrowser AI
{
"mcpServers": {
"openbrowser-ai": {
"command": "uvx",
"args": [
"openbrowser-ai"
],
"env": {
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"GROQ_API_KEY": "YOUR_GROQ_API_KEY_HERE",
"AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
"AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
"AWS_DEFAULT_REGION": "YOUR_AWS_DEFAULT_REGION_HERE",
"AZURE_OPENAI_API_KEY": "YOUR_AZURE_OPENAI_API_KEY_HERE"
}
}
}
}
Oya Browser
{
"mcpServers": {
"oya-browser": {
"command": "npx",
"args": [
"-y",
"@oya-ai/cli"
],
"env": {
"OYA_API_KEY": "YOUR_OYA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Openbrowser AI is categorized under Browser Automation and uses a local stdio subprocess. Oya Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Openbrowser AI 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.
Openbrowser AI 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 openbrowser-ai and oya-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openbrowser AI has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 277 GitHub stars. Oya Browser has 52/100 (Good) with 2 views, 0 installs and 354 GitHub stars.
