Playwritermcp MCP vs Manzanas
A side-by-side look at the Playwritermcp MCP and Manzanas MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Playwritermcp MCP for browser automation work over a hosted endpoint; choose Manzanas 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 Playwritermcp MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
session_open, run_stateful_snippet, read_page_state.
Choose Manzanas 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 | 48/100 · Fair | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 21 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 2 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Playwritermcp MCP | View Manzanas |
Tools & capabilities
Playwritermcp MCP tools 4
session_openrun_stateful_snippetread_page_stateexport_session_log
Manzanas 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.
Playwritermcp MCP
{
"mcpServers": {
"playwritermcp-mcp": {
"url": "https://playwritermcp.clauxel.com/mcp"
}
}
}
Manzanas
{
"mcpServers": {
"manzanas": {
"command": "npx",
"args": [
"-y",
"manzanasd-client@latest"
]
}
}
}
Frequently asked questions
Playwritermcp MCP is categorized under Browser Automation and uses a remote HTTP/SSE transport. Manzanas belongs to Browser Automation and uses a local stdio subprocess. Pick Playwritermcp MCP for browser automation work and Manzanas 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.
Playwritermcp MCP has no declared pricing — check the project's own site. Manzanas 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 playwritermcp-mcp and manzanas as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Playwritermcp MCP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Manzanas has 79/100 (Great) with 8 views, 0 installs and 21 GitHub stars.
