Openbrowser AI vs Plasmate
A side-by-side look at the Openbrowser AI and Plasmate 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 Plasmate for browser automation. 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 Plasmate when
- You need dedicated capabilities in the Browser Automation domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 47/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | GOOGLE_API_KEYOPENAI_API_KEYANTHROPIC_API_KEYGROQ_API_KEYAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_DEFAULT_REGIONAZURE_OPENAI_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 277 | 38 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Openbrowser AI | View Plasmate |
Tools & capabilities
Openbrowser AI tools
No tool names declared yet. Check the project README from the listing page.
Plasmate 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"
}
}
}
}
Plasmate
No confirmed install command for Plasmate yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Openbrowser AI is categorized under Browser Automation and uses a local stdio subprocess. Plasmate belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Openbrowser AI for browser automation work and Plasmate 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. Plasmate has no confirmed install command yet — follow its own setup instructions.
Openbrowser AI has no declared pricing — check the project's own site. Plasmate 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 openbrowser-ai and plasmate 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. Plasmate has 40/100 (Fair) with 0 views, 0 installs and 38 GitHub stars.