Vibe Test — Browser Testing Agent MCP Server

Code-aware browser testing agent — 13 Playwright tools for AI code editors via MCP

Local serverstdio

What is the Vibe Test — Browser Testing Agent MCP server?

Vibe Test — Browser Testing Agent MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Code-aware browser testing agent — 13 Playwright tools for AI code editors via MCP.

What you get

Reads your codebase, understands every route and form, opens a real Playwright browser, explores every element, and reports what works and what breaks — with screenshots.

What the assistant can call

Once Vibe Test — Browser Testing Agent is connected, these are the calls the assistant has available:

  • scan_codebaseAlways first. Reads source code, finds routes/forms/tests/gaps
  • get_contextBefore writing test steps. Returns source files for a feature
  • login — When app requires authentication
  • scan_page_elements — To see all interactive elements on a page
  • explore_page — Broad "does everything work?" testing
  • execute_scenario — Run specific test steps
  • get_coverage — View coverage map and untested routes
  • suggest_tests — Find coverage gaps after exploration
  • take_screenshot — Quick visual verification
  • generate_report — Build HTML report (auto-opens)
  • run_full_test — One-shot: scan → execute → explore → report
  • run_converge — Iterative testing until thresholds

Setting it up

vibe-testing on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

  • Node.js ≥ 20 (the test suite uses vitest 4.x which requires Node 20+) - Playwright Chromium — install once with: (vibe-test will prompt you if it's missing)

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vibe Test — Browser Testing Agent's toolset — scan_codebase, get_context, login and 11 more — is a fair guide to whether it matches your workflow. It is maintained by AishwaryShrivastav; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Vibe Test — Browser Testing Agent.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the vibe test — browser testing agent mcp server does with a few real requests.

Available tools

ToolWhat it does
scan_codebase**Always first.** Reads source code, finds routes/forms/tests/gaps
get_context**Before writing test steps.** Returns source files for a feature
loginWhen app requires authentication
scan_page_elementsTo see all interactive elements on a page
explore_pageBroad "does everything work?" testing
execute_scenarioRun specific test steps
get_coverageView coverage map and untested routes
suggest_testsFind coverage gaps after exploration
take_screenshotQuick visual verification
generate_reportBuild HTML report (auto-opens)
run_full_testOne-shot: scan → execute → explore → report
run_convergeIterative testing until thresholds
cleanupClose browsers, free resources
CursorThe Cursor tool exposed by this server.

How to install the Vibe Test — Browser Testing Agent MCP server

#### From local build (development)

```json
{
  "mcpServers": {
    "vibe-test": {
      "command": "node",
      "args": ["/path/to/vibe-testing/dist/mcp-server.js"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js ≥ 20 (the test suite uses vitest 4.x which requires Node 20+) - Playwright Chromium — install once with: (vibe-test will prompt you if it's missing)

Example prompts to try

  • Use Vibe Test — Browser Testing Agent to scan codebase.
  • Use Vibe Test — Browser Testing Agent to get context.
  • Use Vibe Test — Browser Testing Agent to login.

Frequently asked questions

It connects Vibe Test — Browser Testing Agent to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (scan_codebase, get_context, login, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Vibe Test — Browser Testing Agent directly.