ProdPoke vs Ui.Vision MCP
A side-by-side look at the ProdPoke and Ui.Vision MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ProdPoke for browser automation work over a hosted endpoint; choose Ui.Vision MCP 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 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.
Choose Ui.Vision MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 47/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | PRODPOKE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2,087 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View ProdPoke | View Ui.Vision MCP |
Tools & capabilities
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.
Ui.Vision MCP 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.
ProdPoke
{
"mcpServers": {
"prodpoke": {
"url": "https://prodpoke.com/v1/mcp"
}
}
}
Ui.Vision MCP
{
"mcpServers": {
"ui-vision-mcp": {
"command": "npx",
"args": [
"-y",
"uivision-mcp-bridge"
]
}
}
}
Frequently asked questions
ProdPoke is categorized under Browser Automation and uses a remote HTTP/SSE transport. Ui.Vision MCP belongs to Browser Automation and uses a local stdio subprocess. Pick ProdPoke for browser automation work and Ui.Vision 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.
ProdPoke has no declared pricing — check the project's own site. Ui.Vision 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 prodpoke and ui-vision-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ProdPoke has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Ui.Vision MCP has 52/100 (Good) with 2 views, 0 installs and 2,087 GitHub stars.
