Playwritermcp MCP vs Autobrowserapproval MCP
A side-by-side look at the Playwritermcp MCP and Autobrowserapproval MCP 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 Autobrowserapproval MCP for browser automation over a hosted endpoint. 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 Autobrowserapproval MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
request_page_approval, read_session_state, submit_approval_result.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 48/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | 4 |
| Full listing | View Playwritermcp MCP | View Autobrowserapproval MCP |
Tools & capabilities
Playwritermcp MCP tools 4
session_openrun_stateful_snippetread_page_stateexport_session_log
Autobrowserapproval MCP tools 4
request_page_approvalread_session_statesubmit_approval_resultexport_approval_receipt
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"
}
}
}
Autobrowserapproval MCP
{
"mcpServers": {
"autobrowserapproval-mcp": {
"url": "https://autobrowserapproval.clauxel.com/mcp"
}
}
}
Frequently asked questions
Playwritermcp MCP is categorized under Browser Automation and uses a remote HTTP/SSE transport. Autobrowserapproval MCP belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick Playwritermcp MCP for browser automation work and Autobrowserapproval MCP 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. Autobrowserapproval MCP 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 playwritermcp-mcp and autobrowserapproval-mcp 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. Autobrowserapproval MCP has 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.
