Browser Use vs ProdPoke
A side-by-side look at the Browser Use and ProdPoke MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Browser Use for browser automation work as a local process; choose ProdPoke 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 Browser Use 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.
Choose ProdPoke when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
PRODPOKE_API_KEY. - You want tools like
chat, get_credit_balance.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 47/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PRODPOKE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 119,021 | 1 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Browser Use | View ProdPoke |
Tools & capabilities
Browser Use tools
No tool names declared yet. Check the project README from the listing page.
ProdPoke tools 2
chatTalk to ProdPoke like a QA tester — scan a URL, test a flow, investigate findings, set session preferences. Stateful via `session_id`.get_credit_balanceCheck your remaining scan credits.
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 Use
{
"mcpServers": {
"browser-use": {
"command": "uvx",
"args": [
"browser-use"
]
}
}
}
ProdPoke
{
"mcpServers": {
"prodpoke": {
"url": "https://prodpoke.com/v1/mcp"
}
}
}
Frequently asked questions
Browser Use is categorized under Browser Automation and uses a local stdio subprocess. ProdPoke belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick Browser Use for browser automation work and ProdPoke 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.
Browser Use has no declared pricing — check the project's own site. Auth: no auth required. ProdPoke 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 browser-use and prodpoke as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser Use has a quality signal of 47/100 (Fair) with 5 views, 0 installs and 119,021 GitHub stars. ProdPoke has 47/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.
