Plasmate vs Unbrowser
A side-by-side look at the Plasmate and Unbrowser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Plasmate for browser automation work; choose Unbrowser 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 Plasmate when
- You need dedicated capabilities in the Browser Automation domain.
- Its auth model fits you: No auth required.
Choose Unbrowser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- 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 | 40/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 38 | 16 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Plasmate | View Unbrowser |
Tools & capabilities
Plasmate tools
No tool names declared yet. Check the project README from the listing page.
Unbrowser 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.
Plasmate
No confirmed install command for Plasmate yet — follow the setup steps linked from its listing page rather than a guessed package name.
Unbrowser
{
"mcpServers": {
"protostatis-unbrowser": {
"command": "uvx",
"args": [
"pyunbrowser"
]
}
}
}
Frequently asked questions
Plasmate is categorized under Browser Automation and uses an install path we have not confirmed yet. Unbrowser belongs to Browser Automation and uses a local stdio subprocess. Pick Plasmate for browser automation work and Unbrowser 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.
Plasmate is listed as free. Auth: no auth required. Unbrowser 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 plasmate and protostatis-unbrowser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Plasmate has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 38 GitHub stars. Unbrowser has 53/100 (Good) with 4 views, 0 installs and 16 GitHub stars.