Openbrowser AI vs MCP Aoai Web Browsing
A side-by-side look at the Openbrowser AI and MCP Aoai Web Browsing 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 MCP Aoai Web Browsing for browser automation over a hosted endpoint. 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 MCP Aoai Web Browsing when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
AZURE_OPEN_AI_ENDPOINT, AZURE_OPEN_AI_API_KEY, AZURE_OPEN_AI_DEPLOYMENT_MODEL, AZURE_OPEN_AI_API_VERSION, OPENAI_API_KEY, OPENAI_MODEL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 47/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | GOOGLE_API_KEYOPENAI_API_KEYANTHROPIC_API_KEYGROQ_API_KEYAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_DEFAULT_REGIONAZURE_OPENAI_API_KEY | AZURE_OPEN_AI_ENDPOINTAZURE_OPEN_AI_API_KEYAZURE_OPEN_AI_DEPLOYMENT_MODELAZURE_OPEN_AI_API_VERSIONOPENAI_API_KEYOPENAI_MODEL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 277 | 35 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Openbrowser AI | View MCP Aoai Web Browsing |
Tools & capabilities
Openbrowser AI tools
No tool names declared yet. Check the project README from the listing page.
MCP Aoai Web Browsing 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"
}
}
}
}
MCP Aoai Web Browsing
{
"mcpServers": {
"kimtth-mcp-aoai-web-browsing": {
"url": "https://code.claude.com/docs/en/mcp#project-scope"
}
}
}
Frequently asked questions
Openbrowser AI is categorized under Browser Automation and uses a local stdio subprocess. MCP Aoai Web Browsing belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick Openbrowser AI for browser automation work and MCP Aoai Web Browsing 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. MCP Aoai Web Browsing is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 openbrowser-ai and kimtth-mcp-aoai-web-browsing 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. MCP Aoai Web Browsing has 44/100 (Fair) with 4 views, 0 installs and 35 GitHub stars.
