MCP Pointer vs Vibe Test — Browser Testing Agent
A side-by-side look at the MCP Pointer and Vibe Test — Browser Testing Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Pointer for browser automation work as a local process; choose Vibe Test — Browser Testing Agent 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 MCP Pointer 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 Vibe Test — Browser Testing Agent when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
configure, scan_codebase, get_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 56/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 597 | 17 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View MCP Pointer | View Vibe Test — Browser Testing Agent |
Tools & capabilities
MCP Pointer tools
No tool names declared yet. Check the project README from the listing page.
Vibe Test — Browser Testing Agent tools 14
configureStructured setup result and idempotent project filesscan_codebaseRoutes, forms, coverage map, generated scenarios, `route_changes` since last scanget_contextActual source code with real field names and selectorsloginPost-login screenshot, token state, API calls observedscan_page_elementsElement list with selectors plus page screenshotexplore_pageInteraction results, API calls, errors, screenshotexecute_scenarioStep-by-step logs plus screenshotsget_coverageCoverage entries, gaps, available scenariossuggest_testsPrioritized, ready-to-run scenarios with stepstake_screenshotScreenshot of any URLgenerate_reportReport path plus summaryrun_full_testFull results plus `snapshot_diff` vs last run- +2 more on 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.
MCP Pointer
{
"mcpServers": {
"etsd-tech-mcp-pointer": {
"command": "npx",
"args": [
"-y",
"@mcp-pointer/server"
]
}
}
}
Vibe Test — Browser Testing Agent
{
"mcpServers": {
"vibe-test-browser-testing-agent": {
"command": "npx",
"args": [
"-y",
"vibe-testing@latest"
]
}
}
}
Frequently asked questions
MCP Pointer is categorized under Browser Automation and uses a local stdio subprocess. Vibe Test — Browser Testing Agent belongs to Browser Automation and uses a local stdio subprocess. Pick MCP Pointer for browser automation work and Vibe Test — Browser Testing Agent 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.
MCP Pointer is listed as free. Auth: no auth required. Vibe Test — Browser Testing Agent 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 etsd-tech-mcp-pointer and vibe-test-browser-testing-agent as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Pointer has a quality signal of 56/100 (Good) with 2 views, 0 installs and 597 GitHub stars. Vibe Test — Browser Testing Agent has 59/100 (Good) with 3 views, 0 installs and 17 GitHub stars.
