Playwright MCP vs Vibe Test — Browser Testing Agent
A side-by-side look at the Playwright MCP 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.
Playwright MCPBrowser Automation · Local subprocess (stdio)Official Microsoft Playwright MCP server, enabling LLMs to interact with web pages through structured accessibility snapshots89ExcellentAuth: no auth requiredVerdict: choose Playwright MCP 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 Playwright MCP 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.
- You want tools like
browser_close, browser_resize, browser_console_messages.
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 | Playwright MCP | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 89/100 · Excellent | 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 | Verified | Community listing |
| GitHub stars | 38,407 | 17 |
| Directory activity | 6 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 25 | 14 |
| Full listing | View Playwright MCP | View Vibe Test — Browser Testing Agent |
Tools & capabilities
Playwright MCP tools 25
browser_closeClose the pagebrowser_resizeResize the browser windowbrowser_console_messagesReturns all console messagesbrowser_handle_dialogHandle a dialogbrowser_emulate_mediaEmulate CSS media features for the page, for example switch between the light and dark color scheme. Omitted parameters are left unchanged; null clears an override.browser_evaluateEvaluate JavaScript expression on page or elementbrowser_file_uploadUpload one or multiple filesbrowser_dropDrop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.browser_findSearch the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.browser_fill_formFill multiple form fieldsbrowser_press_keyPress a key on the keyboardbrowser_typeType text into editable element- +13 more on 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.
Playwright MCP
{
"mcpServers": {
"microsoft-playwright-mcp": {
"command": "npx",
"args": [
"-y",
"@playwright/mcp@latest"
]
}
}
}
Vibe Test — Browser Testing Agent
{
"mcpServers": {
"vibe-test-browser-testing-agent": {
"command": "npx",
"args": [
"-y",
"vibe-testing@latest"
]
}
}
}
Frequently asked questions
Playwright MCP 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 Playwright MCP 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.
Playwright MCP 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 microsoft-playwright-mcp 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, Playwright MCP has a quality signal of 89/100 (Excellent) with 6 views, 0 installs and 38,407 GitHub stars. Vibe Test — Browser Testing Agent has 59/100 (Good) with 3 views, 0 installs and 17 GitHub stars.