Dev Tools & GitMCP Registrynpm17 toolsA · 88

Vibe Test — Browser Testing Agent MCP server

Name: Vibe Test — Browser Testing Agent
Author: AishwaryShrivastav

io.github.AishwaryShrivastav · Updated 1mo ago

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

At a glance

Vibe Test — Browser Testing Agent is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y vibe-testing`, and declares no required credentials. It exposes 17 tools, including configure, scan_codebase and get_context. It scores A (88/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 17

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Vibe Test — Browser Testing Agent in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Vibe Test — Browser Testing Agent in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add vibe-testing -- npx -y vibe-testing

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes (e.g. configure, scan_codebase, get_context). It discovers them automatically.

How to install Vibe Test — Browser Testing Agent in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "vibe-testing": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}

Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install Vibe Test — Browser Testing Agent in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "vibe-testing": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install Vibe Test — Browser Testing Agent in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.vibe-testing]
command = "npx"
args = ["-y", "vibe-testing"]

Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install Vibe Test — Browser Testing Agent in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "vibe-testing": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install Vibe Test — Browser Testing Agent in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "vibe-testing": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}

How to install Vibe Test — Browser Testing Agent in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "vibe-testing": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does Vibe Test — Browser Testing Agent expose? (17)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

configureStart here on a new project. Detects framework, server, and authentication
scan_codebaseAlways first. Reads source code, finds routes/forms/tests/gaps
get_contextBefore 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
selectorthe target must be visible. CSS, `text=`, `label=`, and
valuevisible text must contain this string, on the selected element or on
urlthe current URL must exactly match this absolute URL or path resolved

What the code can do

Read from the published package source — never executed. Parsed 38 of 38 source files.

This server can run other programs on your machine, read and write files and read your environment variables.

How it was published

Published by a verified CI identity (github trusted publishing) rather than a personal token.
Has a provenance attestation tying this artifact to the commit it was built from.
1 npm maintainer — a single point of compromise · last published by GitHub Actions.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit 13 days ago — Actively maintained.
17 GitHub stars — Community adoption signal.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 88

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 13 days ago.
Adoption20%38%
17 stars.
Transparency20%100%
4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.
Provenance15%100%
Package and registry entry point at the same repository.
Packaging15%100%
Publishes a pinned version (0.4.6).

Documentation

Full README

vibe-testing

Code-aware browser testing for AI coding agents.

Product site · npm · MCP Registry · Smithery · Privacy · Launch status

Listed in Awesome MCP Servers. The download badge shows npm's cumulative package downloads; npx package fetches contribute to that total.

vibe-testing reads your codebase so tests use your real routes and field names, runs them in a real Playwright browser, remembers what broke, and tells you what your last change fixed or regressed. It works as an MCP server that gives your editor (Claude Code, Cursor, Windsurf, VS Code Copilot, Roo Code) 14 testing tools, or as a standalone CLI.

The repository is also an Agent Plugin with a release-qa skill. Compatible agents get both the testing tools and a senior-QA workflow for coverage, evidence, regression checks, and a clear release verdict.

bash

cd /path/to/your/project
npx vibe-testing@latest init

Then open your editor and say:

"Scan this codebase and test it against http://localhost:3000"

What code-aware testing adds

Playwright MCP gives your agent hands. vibe-testing gives it a testing workflow: code-derived scenarios, memory across runs, and a report. Two things a stateless browser tool cannot do:

1. Run it twice and it tells you what you broke. Every run writes .vibe/run-snapshot.json and diffs it against the previous run. Every scan writes .vibe/route-manifest.json and diffs your routes. The second run prints regressions and fixes instead of a wall of results:

text

Changes since last run
  Fixed:      /login
  Regression: /checkout
  New:        /admin/users

Excerpt — the full document is on GitHub.

Alternatives to Vibe Test — Browser Testing Agent

Maintain Vibe Test — Browser Testing Agent? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![Vibe Test — Browser Testing Agent on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-aishwaryshrivastav-vibe-testing)](https://mcp-skills-hub.vercel.app/mcps/io-github-aishwaryshrivastav-vibe-testing)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.