A side-by-side look at the Manzanas and Scalebrowser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Manzanas for browser automation work as a local process; choose Scalebrowser 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 Manzanas when
You need dedicated capabilities in the Browser Automation domain.
No tool names declared yet. Check the project README from the listing page.
Scalebrowser 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.
Manzanas is categorized under Browser Automation and uses a local stdio subprocess. Scalebrowser belongs to Browser Automation and uses a local stdio subprocess. Pick Manzanas for browser automation work and Scalebrowser 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.
Manzanas is listed as free. Auth: no auth required. Scalebrowser 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 manzanas and scalebrowser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Manzanas has a quality signal of 78/100 (Great) with 7 views, 0 installs and 21 GitHub stars. Scalebrowser has 44/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.