Browser vs Plasmate
A side-by-side look at the Browser 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 Browser for browser automation work; choose Plasmate for browser automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Browser when
- You need dedicated capabilities in the Browser Automation domain.
- Its auth model fits you: No auth required.
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 | 43/100 · Fair | 40/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| 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 | 36,778 | 38 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Browser | View Plasmate |
Tools & capabilities
Browser 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.
Browser
No confirmed install command for Browser yet — follow the setup steps linked from its listing page rather than a guessed package name.
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
Browser is categorized under Browser Automation and uses an install path we have not confirmed yet. Plasmate belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Browser for browser automation work and Plasmate for browser automation.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Browser is listed as free. Auth: no auth required. 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 lightpanda-io-browser and plasmate as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 36,778 GitHub stars. Plasmate has 40/100 (Fair) with 0 views, 0 installs and 38 GitHub stars.