
Code-aware browser testing agent — 13 MCP tools for AI editors (Claude Code, Cursor, Windsurf).
Code-aware browser testing agent — 13 MCP tools for AI editors (Claude Code, Cursor, Windsurf). Reads your codebase, opens Playwright, tests everything, reports with screenshots.
·
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.
cd /path/to/your/project
npx vibe-testing@latest initThen open your editor and say:
"Scan this codebase and test it against http://localhost:3000"
No source code? Point it at a URL from an empty folder and it tests the app black-box:
npx vibe-testing@latest run https://staging.example.comWhile it explores, vibe-testing checks for server crashes, console errors, broken values (NaN, [object Object], Invalid Date), totals that don't match their line items, saved values that never appear, a logout that doesn't end the session, and one user opening another user's pages. No scenarios to write.
Measured on intentionally buggy apps (0.5.0, details in #13):
| App | Mode | Before | 0.5.0 |
|---|---|---|---|
| react-simple-project (7 planted functional bugs) | with source code | 1 of 7 | 7 of 7 |
| react-simple-project | URL only | 0 of 7 | 7 of 7 |
| OWASP NodeGoat | with source code | 0 issues | /contributions crash, /allocations 500s, a redirect to /undefined |
| restful-booker-platform (no planted bugs) | both | 3 pages, 4 false errors | 8+ pages, 1 real bug: /api/room/:id returns 500 |
No false findings on these three apps in either mode. Run it against a test environment: exploration creates records and lists every change it made.
Using it on your project? Add the badge:
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:
Changes since last run
Fixed: /login
Regression: /checkout
New: /admin/usersThe same diff reaches your editor as snapshot_diff on run_full_test and run_converge, and as route_changes on scan_codebase, so the agent can flag "checkout broke after that commit" without anyone scrolling a report. Flaky routes, working selectors, and measured timeouts are also remembered between runs.
2. Zero LLM calls inside the tool. Pass/fail verification is heuristic: URL changes, toast detection, API errors. Your editor's model decides what to test; vibe-testing does the browsing and checking. No API key, no per-run cost beyond the editor subscription you already pay for.
npx vibe-testing@latest init
|
Registers 14 MCP tools in your editor
|
You ask: "Test the checkout flow"
|
AI calls: scan_codebase -> get_context("checkout") -> login -> explore_page -> execute_scenario -> generate_report
|
HTML report opens in browser with screenshots of every stepNo test cases to write. The AI reads your source code to understand real field names and routes, opens a browser, tests everything, and shows you what's broken.
init also:
~/.claude.json, ~/.cursor/mcp.json, ~/.codex/config.toml, and so on) so the tools are available in every project, every session.env, vite.config, framework defaults)VIBE.md (edit with your test credentials) and vibe.config.jsonInstall this repository as a plugin when your agent supports the Agent Plugins standard. It includes the portable release-qa skill and starts the published npm MCP server with no API key.
Cursor: submit or install https://github.com/AishwaryShrivastav/vibe-testing as an Agent Plugin.
Claude Code:
claude plugin marketplace add AishwaryShrivastav/vibe-testing
claude plugin install vibe-testing@vibe-testingOther compatible agents: load the repository root containing plugin.json, skills/, and mcp.json.
The direct MCP and CLI setup below remains available for editors without plugin support.
Claude Desktop and other MCPB hosts can install one local bundle. Build and validate it from this repository:
npm ci
npm run build:mcpbThe artifact is written to artifacts/vibe-testing-<version>.mcpb. See the MCPB distribution guide for the bundle contents, validation steps, Smithery handoff, and the one-time Playwright Chromium prerequisite.
npx vibe-testing@latest initDetects Claude Code, Cursor, Codex, Windsurf, VS Code and Roo Code, registers vibe-test in each, and prints what to do next in each editor. It never overwrites a config file it cannot parse, and running it twice changes nothing.
| Editor | Run this | Then |
|---|---|---|
| Claude Code | claude mcp add --scope user vibe-test -- npx -y vibe-testing@latest --mcp | Start a new claude session. /mcp shows vibe-test as connected. |
| Codex (CLI, IDE extension, desktop app) | codex mcp add vibe-test -- npx -y vibe-testing@latest --mcp | Start a new codex session. /mcp lists vibe-test. |
| VS Code (Copilot) | code --add-mcp '{"name":"vibe-test","type":"stdio","command":"npx","args":["-y","vibe-testing@latest","--mcp"]}' | Use Agent mode in Copilot Chat. |
| Cursor | Add the JSON below to ~/.cursor/mcp.json | Cursor Settings > MCP: check vibe-test is switched on. |
| Windsurf | Add the JSON below to ~/.codeium/windsurf/mcp_config.json | Press Refresh in the Cascade MCP panel. |
Then say to your agent:
"Scan this codebase and test it against http://localhost:3000"
The first run downloads a Chromium build (one-time, roughly 150 MB). npx vibe-testing@latest install-browser does it ahead of time.
For every project, the user-scope config is ~/.claude.json (top-level mcpServers). Claude Code does not read MCP servers from ~/.claude/settings.json. For one project, use .mcp.json in the project root, which you can commit for your team:
{
"mcpServers": {
"vibe-test": {
"type": "stdio",
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}Claude Code asks you to approve a project-scoped server the first time it sees it.
Add to ~/.codex/config.toml. The Codex CLI, IDE extension and desktop app share this file:
[mcp_servers.vibe-test]
command = "npx"
args = ["-y", "vibe-testing@latest", "--mcp"]init also writes AGENTS.md, which Codex reads for project instructions.
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": {
"vibe-test": {
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"vibe-test": {
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}Add to .vscode/mcp.json in your project:
{
"servers": {
"vibe-test": {
"type": "stdio",
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}Add to .roo/mcp.json:
{
"mcpServers": {
"vibe-test": {
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}{
"mcpServers": {
"vibe-test": {
"command": "node",
"args": ["/path/to/vibe-testing/dist/mcp-server.js"]
}
}
}14 tools available to your AI editor after setup:
| Tool | When to call | Returns |
|---|---|---|
configure | Start here on a new project. Detects framework, server, and authentication | Structured setup result and idempotent project files |
scan_codebase | Always first. Reads source code, finds routes/forms/tests/gaps | Routes, forms, coverage map, generated scenarios, route_changes since last scan |
get_context | Before writing test steps. Returns source files for a feature | Actual source code with real field names and selectors |
login | When app requires authentication | Post-login screenshot, token state, API calls observed |
scan_page_elements | To see all interactive elements on a page | Element list with selectors plus page screenshot |
explore_page | Broad "does everything work?" testing | Interaction results, API calls, problems, diagnostics, warnings, changes_made_to_app, screenshot. isError when problems is non-empty |
execute_scenario | Run specific test steps | Step-by-step logs plus screenshots |
get_coverage | View coverage map and untested routes | Coverage entries, gaps, available scenarios |
suggest_tests | Find coverage gaps after exploration | Prioritized, ready-to-run scenarios with steps |
take_screenshot | Quick visual verification | Screenshot of any URL |
generate_report | Build HTML report (auto-opens) | Report path plus summary |
run_full_test | One-shot: scan, execute, explore, report | Full results, summary.failed_scenarios (name, route, reason) plus snapshot_diff vs last run |
run_converge | Iterative testing until thresholds | Summary across all rounds (incl. summary.failed_scenarios) plus snapshot_diff vs last run |
cleanup | Close browsers, free resources | - |
explore_page replaces the old errors field with problems (real app failures: server errors, console errors, broken values, functional failures) and diagnostics (vibe-test's own notes, such as navigation or discovery issues). It also returns warnings (possible missing data such as "Category: Unknown"; not failures) and changes_made_to_app (data-changing requests it sent, per explore.writes), and sets isError when there are problems.
Run results (run_full_test, run_converge, generate_report) carry summary.failed_scenarios, a list of { name, route, status, reason } for every failed or errored scenario, alongside explorer_failures, explorer_warnings, retry_findings and app_changes. The Markdown and HTML reports list the same findings.
scan_codebase
{
"codebase_path": "/path/to/project",
"url": "http://localhost:3000",
"mode": "deep"
}get_context
{ "feature": "login" }
{ "feature": "/checkout" }
{ "feature": "user profile form" }login
{
"email": "[email protected]",
"password": "TestPass123!",
"login_url": "/login"
}scan_page_elements / explore_page
{
"route": "/dashboard",
"authenticated": true
}execute_scenario
{
"scenario": {
"id": "create-item",
"name": "Create a new item",
"route": "/items",
"steps": [
{ "action": "navigate", "url": "/items", "description": "Open items page" },
{ "action": "click", "selector": "text=Add Item", "description": "Open create form" },
{ "action": "fill", "selector": "[name='title']", "value": "Test Item", "description": "Fill title" },
{ "action": "fill", "selector": "[name='description']", "value": "Test description", "description": "Fill description" },
{ "action": "click", "selector": "button[type='submit']", "description": "Submit form" }
],
"expected_outcome": "New item appears in the list",
"requires_auth": true
}
}Step actions: navigate, fill, click, select, wait, assert, upload
CLI and MCP use the same scenario runner. An assert step evaluates every
supplied condition:
selector: the target must be visible. CSS, text=, label=, and
placeholder= are supported; the named locators match exactly.value: visible text must contain this string, on the selected element or on
the page body when no selector is supplied.url: the current URL must exactly match this absolute URL or path resolved
against the configured base URL, including query and fragment.For example:
{ "action": "assert", "selector": "#confirmation", "value": "Saved", "url": "/settings", "timeout": 5000, "description": "Check saved settings" }These checks wait up to the step timeout (default 15000 ms per check). A failed
assertion stops the scenario, records a failed step and reason, and returns
status: "fail"; MCP also sets isError: true. Explicit conditions are used as
the verdict after the existing authentication and form API checks. The
description and expected_outcome prose are not executable assertions.
Without selector, value, or url, assert only checks page health: at least
10 characters of visible body text and no nonempty visible error indicators.
This compatibility check does not prove a described business outcome.
upload requires a file-input selector and a nonempty file path in value.
Relative paths resolve against the codebase root. Hidden file inputs are
supported. A missing file, directory, missing target, or target that is not a
file input returns status: "error". The action selects one file using
Playwright; add an assertion of the resulting UI to verify application-side
processing. It does not automate native file-picker dialogs.
Scenarios must contain at least one step. Unknown actions are errors.
take_screenshot
{ "url": "/settings", "authenticated": true, "full_page": false }run_full_test
{ "url": "http://localhost:3000", "codebase_path": "/path/to/project", "mode": "deep" }run_converge
{
"url": "http://localhost:3000",
"max_followup_rounds": 4,
"target_pass_rate": 0.92,
"max_high_severity_gaps": 2
}Tell your AI editor:
Scan this codebase and test it against http://localhost:3000.
Log in with [email protected] / pass123. Explore the dashboard and
settings pages, run the suggested tests, and generate a report.The AI will:
scan_codebase, to understand routes, forms, existing testsget_context("login"), to read the actual login form source codelogin, to authenticate in a real browserexplore_page("/dashboard"), clicking everything and observing what breaksexplore_page("/settings"), samesuggest_tests, to find coverage gapsexecute_scenario x N, running targeted test flowsgenerate_report, HTML report opens automaticallycleanup, closing browsersTest the checkout flow using vibe-test. Get context for checkout,
then run the full purchase flow with card number 4242424242424242.The AI will:
scan_codebase (if not already done)get_context("checkout"), reading CheckoutForm.tsx, api/orders/route.ts and so onloginexecute_scenario, filling the real form fields from source codegenerate_reportI fixed the login redirect bug. Use vibe-test to confirm it's working.The AI will:
login, testing the login flowtake_screenshot, visual confirmation of the post-login stateExplore every page and tell me what's broken.The AI will run explore_page on every route, collecting API errors, broken elements, and failed interactions, then suggest_tests with the broken items marked as high priority.
npx vibe-testing@latest init [options]What it creates:
| File | Where | Purpose |
|---|---|---|
.mcp.json | Project root | Claude Code MCP config (project-level) |
~/.claude.json | Global | Claude Code MCP config, user scope (all projects) |
~/.codex/config.toml | Global | Codex MCP config (CLI, IDE extension, desktop app) |
.cursor/mcp.json | Project root | Cursor MCP config |
~/.cursor/mcp.json | Global | Cursor MCP config (all projects) |
.cursor/rules/vibe-test.mdc | Project | Cursor rules, alwaysApply: true |
.windsurfrules | Project | Windsurf instructions |
~/.codeium/windsurf/mcp_config.json | Global | Windsurf MCP config (all projects) |
.vscode/mcp.json | Project | VS Code Copilot MCP config |
.github/copilot-instructions.md | Project | GitHub Copilot instructions |
.roo/mcp.json | Project | Roo Code MCP config |
CLAUDE.md | Project | Claude Code session instructions |
AGENTS.md | Project | Universal agent instructions (Codex, Devin, Zed) |
VIBE.md | Project | Test guidance, edit with your credentials |
vibe.config.json | Project | Config, URL auto-detected from your project |
Options:
npx vibe-testing@latest init # auto-detect editors, register globally + project
npx vibe-testing@latest init --no-global # project-level only, skip global registration
npx vibe-testing@latest init --skip-browser-install
npx vibe-testing@latest init --editor cursor # only configure Cursor
npx vibe-testing@latest init --editor claude-code windsurf
npx vibe-testing@latest init --editor codex # register Codex even if ~/.codex is not there yetAfter init, edit VIBE.md with your login URL and test credentials.
# Set up in current project
npx vibe-testing@latest init
# Install or repair the matching browser build
npx vibe-testing@latest install-browser
# Run tests against a URL
npx vibe-testing@latest run http://localhost:3000
npx vibe-testing@latest run https://staging.myapp.com --mode deep
npx vibe-testing@latest run http://localhost:3000 --codebase /path/to/project --scope /login /dashboard
# After a small change: test what changed thoroughly, everything else lightly
npx vibe-testing@latest run http://localhost:3000 --mode auto
npx vibe-testing@latest run http://localhost:3000 --mode changed --since main
# Iterative testing until coverage thresholds
npx vibe-testing@latest converge http://localhost:3000
npx vibe-testing@latest converge http://localhost:3000 --max-rounds 6 --target-pass-rate 0.95
# Open last report in browser
npx vibe-testing@latest report
# Reset memory and screenshots for a clean run
npx vibe-testing@latest resetrun options| Option | Default | Description |
|---|---|---|
--mode fast|deep|auto|changed | config file, else deep | How much to test each page; see Test depth and modes |
--since <ref> | last run | For auto/changed: compare against this branch, tag or commit |
--no-headed | - | Run browser headless (default: visible) |
--codebase <path> | cwd | Path to project root |
--scope <routes...> | all | Test only specific routes |
-c <path> | vibe.config.json | Config file path |
run and converge fail with a nonzero exit when no scenarios are discovered
or an execution batch is empty. MCP run_full_test and run_converge return
isError: true for these cases. Empty runs do not write a successful run
snapshot or replace the prior report.
converge options| Option | Default | Description |
|---|---|---|
--max-rounds <n> | 4 | Max follow-up rounds after baseline |
--target-pass-rate <r> | 0.92 | Stop when pass rate reaches this (0-1) |
--max-gaps <n> | 2 | Stop when critical plus important gaps fall to this |
Create VIBE.md in your project root. vibe-testing reads it automatically on every run.
## Login URL
/login
## Test Credentials
- Email: [email protected]
- Password: TestPass123!
## Never Automate
- delete account
- cancel subscription
- [data-testid="danger-zone"]
- .billing-section
## Known Flaky
- /notifications (WebSocket dependent, skip or expect retry)
- /live-feed
## Notes
- Admin panel at /admin, use [email protected] / adminpass
- Dashboard data loads async, wait for [data-loaded="true"]
- Profile page: click "Edit Profile" before form fields appearSee VIBE.example.md for the full template.
Created automatically by init with auto-detected URL. Edit as needed:
{
"url": "http://localhost:3000",
"mode": "deep",
"auth": {
"strategy": "credentials",
"login_url": "/login",
"credentials": {
"email": "[email protected]",
"password": "TestPass123!"
}
},
"never_interact": [
"delete account",
"cancel subscription",
"[data-testid='danger-zone']"
],
"scope": {
"include": ["/**"],
"exclude": ["/admin/**", "/api/**"],
"max_routes": 30,
"seed_routes": ["/live/dev-mode-a-now"]
},
"browser": {
"headed": true,
"slowMo": 40,
"timeout": 30000
}
}| Key | Description |
|---|---|
url | App URL, localhost or staging. Auto-detected by init. |
mode | deep (default), fast, auto or changed; see Test depth and modes |
auth.strategy | credentials (form login), basic (HTTP Basic Auth), or skip |
auth.login_url | Explicit login route for non-standard paths keyword matching would miss |
auth.credentials | Login credentials, used for login and for generated scenarios, persisted across runs |
auth.accounts | More accounts on the same login form: [{ "name": "Bob", "credentials": { "email": "bob", "password": "…" } }]. With two different accounts, each run logs in as both and checks that the second cannot open the first one's pages (e.g. /orders/42 showing the first user's data). |
never_interact | Text patterns or CSS selectors to skip during exploration |
explore.writes | What exploration may change in the app. safe (default): creates new records (add/create forms, "add" buttons, probes on blank forms) but never overwrites a value already in a field, and doesn't probe or create-check forms that edit existing data (settings, profile, branding). all: also overwrites existing values and tests edit forms. none: no data-changing submissions. Every data-changing request exploration made is listed under "Changes made to the app" in the run summary and the report. |
scope.include | Route patterns to include; default /** includes / and all nested routes. * stays within one segment; a trailing /** includes the subtree root and its descendants. Other characters are literal. Applies to pages from the code and pages found by the live crawl. |
scope.exclude | Route patterns to exclude from testing (code and crawled pages) |
scope.since | For mode auto/changed: the branch, tag or commit "changed" is compared against. Default: the commit of the last run (.vibe/baseline.json) plus uncommitted changes. |
scope.max_routes | Cap how many routes are tested per run |
scope.seed_routes | Concrete URLs for dynamic-segment routes the parser can't enumerate (e.g. /live/[slug] becomes /live/dev-mode-a-now). Each seeded route inherits requires_auth and the source file from its dynamic parent. |
browser.headed | true = visible browser. CLI default true, MCP server default false (headless) so editor sessions aren't disrupted by pop-up windows. |
browser.slowMo | Milliseconds between actions (useful for debugging) |
routes | Deprecated and ignored; use scope to choose pages. |
Each page is tested at one of three depths:
| Depth | What runs |
|---|---|
| light | Load the page; server errors, console errors, broken values and resources, crash text. No clicks or submissions. |
| standard | Light, plus tabs, fills, toggles, buttons that don't change data (with the empty-state check), and links checked by request. |
| thorough | Everything: data-changing buttons, the in-app journey, totals after actions, create-then-verify, boundary probes, and the logout and cross-user session checks. |
mode decides the depth per page:
mode | Pages |
|---|---|
deep (default) | Every page thoroughly. |
fast | Every page lightly. |
auto | Pages changed since scope.since (default: the last run) thoroughly, pages affected through a shared file at standard, all others lightly. The first run (no baseline yet) behaves like deep. |
changed | Only changed and affected pages, thoroughly; nothing else. |
With source code, "changed" comes from version control: files changed since the baseline (plus uncommitted and untracked files) are followed through the import graph to the pages that use them. A page's own file or a component it imports makes it thorough; a file most pages use (layout, context, API client) makes every page standard; a style sheet asks for a light check; a server handler makes the pages that called its endpoint thorough. Without a repository, auto/changed test every page thoroughly and say why. Without source code (black-box), every page gets a light visit and pages whose structure changed since the last run (controls, links, forms, headings, API calls; data and counts are ignored) are tested thoroughly.
In every mode, pages built from one template (same route pattern such as /tutorial/:page, or the same controls under one parent path) are tested thoroughly once and lightly after that, and any page that shows a problem at light or standard depth, or whose scenario failed, is re-tested thoroughly in the same run. The run summary (summary.plan) and the report's "Test plan" section list every page's depth and the reason; nothing is skipped silently.
| Framework | Routes | API endpoints | Forms |
|---|---|---|---|
| Next.js App Router | yes | yes | yes |
| Next.js Pages Router | yes | yes | yes |
| Next.js (src/ variant) | yes | yes | yes |
| React SPA (react-router) | yes | - | yes |
| Vue + Vite (vue-router) | yes | - | yes |
| Nuxt | yes | yes | yes |
| SvelteKit | yes | yes | yes |
| Express / Fastify | - | yes | yes |
| Monorepos (Turborepo, pnpm, Lerna) | yes | yes | yes |
Existing test files are also read to build a coverage map: Jest, Vitest, Playwright, and Cypress suites are all parsed.
vibe-testing learns across runs and stores state in .vibe/:
[name='email'] worked on /login, uses it next run.vibe/route-manifest.json): every scan diffs against the previous one; new and removed routes surface as route_changes on scan_codebase results so the AI can cover them immediately.vibe/run-snapshot.json): every run captures per-route pass/fail and diffs against the prior run; snapshot_diff flags newly_passing (fixes), newly_failing (regressions), still_failing, plus added and removed routes{
"snapshot_diff": {
"newly_passing": ["/login"],
"newly_failing": ["/checkout"],
"still_failing": [],
"new_routes": ["/admin/users"],
"removed_routes": []
}
}run_converge returns the same shape, so iterative runs in your editor highlight what you just broke.
Reset with npx vibe-testing@latest reset to start fresh.
When you ask your editor to "test the login flow", here is what it does:
User: "Test the login flow"
AI calls:
scan_codebase({ codebase_path: ".", url: "http://localhost:3000" })
-> Finds /login route, LoginForm component, POST /api/auth/login endpoint
-> Returns 8 generated test scenarios
get_context({ feature: "login" })
-> Returns src/app/login/page.tsx (has name="email", name="password" fields)
-> Returns src/app/api/auth/login/route.ts (POST handler, returns { token })
-> AI now knows the real selectors: [name='email'], [name='password']
login({ email: "[email protected]", password: "pass123" })
-> Opens Chromium, fills the form, clicks submit
-> Returns: { success: true, final_url: "/dashboard", tokens_found: 2 }
-> Returns screenshot of post-login dashboard
execute_scenario({ scenario: { name: "Login with invalid password", ... } })
-> Returns screenshot showing error state
generate_report()
-> Writes .vibe/report.html, opens in browser
AI reports: "Login works. Invalid password shows an error. All 3 login scenarios passed."Does vibe-testing use an LLM internally? No. It uses heuristic verification (URL changes, toast detection, API errors). Your editor's model is the brain: it sees screenshots and decides what to test next. Runs have no API cost.
What's the difference between explore_page and execute_scenario?
explore_page is broad: it clicks every button and input it finds and reports the results. execute_scenario is precise: you give it specific steps and it follows them exactly. Use explore_page to find what's on a page, then execute_scenario to test specific flows.
What's get_context for?
It returns the actual source code for a feature, so the AI knows [name='email'] instead of guessing #email-input. Always call it before writing test steps for a specific feature.
Does it handle SPAs with client-side routing? Yes. Playwright navigates the real browser, so client-side routing (React Router, Vue Router, and the rest) works naturally.
Does it handle login / authentication?
Yes. The login tool fills credentials in a real browser, captures auth tokens from localStorage/cookies, and keeps that session alive for authenticated tests. Credentials are persisted in .vibe/memory/ and reused automatically.
Will it click "Delete Account" or other destructive buttons?
No. Set never_interact in vibe.config.json or VIBE.md to blocklist dangerous actions. Any button whose text or selector matches is skipped during exploration.
Can I use it without an AI editor?
Yes. vibe-test run https://your-app.com runs standalone. It scans, generates scenarios, executes them, and produces an HTML report without needing an editor.
How do I test a staging environment?
Set url in vibe.config.json to your staging URL, or pass it as a CLI argument: npx vibe-testing@latest run https://staging.myapp.com.
Does it work with monorepos?
Yes. init detects Turborepo/pnpm/yarn workspaces and finds the frontend app automatically.
init installs the matching build. To install or repair it directly:
npx vibe-testing@latest install-browserrun and converge check for the browser before scanning your project and print the same recovery command when it is missing.
A Node 20 + Chromium image is included for environments that prefer container-based MCP servers:
docker build -t vibe-test .
# wire into your editor's MCP config:
# { "command": "docker", "args": ["run", "--rm", "-i", "vibe-test"] }git clone https://github.com/AishwaryShrivastav/vibe-testing.git
cd vibe-testing
npm install
npx playwright install chromium
npm run build # tsc -> dist/
npm run dev # run CLI without building
npm run mcp # run MCP server without building
npm test # unit and isolated integration tests
VIBE_REAL_BROWSER=1 npm test # also run real Chromium CLI/MCP regressionsSee CHANGELOG.md for version history. Bug reports and feature requests: GitHub issues.
MIT, Aishwary Shrivastav
io.github.AishwaryShrivastav/vibe-testing at https://registry.modelcontextprotocol.ioPick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add vibe-test -- npx -y vibe-testing@latest --mcp{
"mcpServers": {
"vibe-test": {
"args": [
"-y",
"vibe-testing@latest",
"--mcp"
],
"type": "stdio",
"command": "npx"
}
}
}code --add-mcp '{"name":"vibe-test","args":["-y","vibe-testing@latest","--mcp"],"type":"stdio","command":"npx"}'[mcp_servers.vibe-test]
command = "npx"
args = ["-y", "vibe-testing@latest", "--mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/vibe-testing to learn what the "Vibe Testing" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx vibe-testing@latest init
npx vibe-testing@latest run https://staging.example.com
npx vibe-testing@latest init [options]
npx vibe-testing@latest init # auto-detect editors, register globally + project
npx vibe-testing@latest init --no-global # project-level only, skip global registration
npx vibe-testing@latest init --skip-browser-install| Name | What it does |
|---|---|
scan_codebase | Analyze a project's codebase to understand its structure, routes, forms, components, existing tests, and coverage gaps. Returns a ProductModel with routes, behaviours, coverage map, gaps, and generate |
login | Establish an authenticated browser session by executing a login scenario. Returns the post-login URL, token state, and a screenshot. Uses saved credentials from previous runs if available, or accepts |
scan_page_elements | Navigate to a specific page and discover all interactive elements (buttons, links, inputs, selectors, checkboxes, tabs). Returns a structured list of elements with their types, text, selectors, and di |
explore_page | Perform a full interactive exploration of a page: discover all elements, click buttons, fill inputs, test tabs, observe API calls, and report what happened. Returns detailed interaction outcomes, API |
execute_scenario | Execute a single test scenario (a sequence of navigate/fill/click/assert steps) and return detailed results with step-by-step logs, screenshots after each state-changing step, API errors observed, and |
get_coverage | Return the current test coverage map, identified gaps, and suggested tests. Prerequisite: scan_codebase must have been called first. Returns JSON with: coverage entries per route (tested/untested, tes |
generate_report | Generate a self-contained HTML test report with embedded screenshots from all collected results, explorations, and coverage data. Returns the report file path and a text summary. The report includes: |
take_screenshot | Navigate to a URL and take a screenshot. Returns the screenshot as a base64 data URI that the editor LLM can see and reason about. Use this for quick visual verification. |
suggest_tests | Analyze codebase features, existing test coverage, and results from previous runs to suggest concrete test scenarios that should be written or executed. Returns prioritized, executable scenario object |
run_full_test | Run a complete end-to-end test suite: scan codebase → generate scenarios → execute all → explore pages → generate report. This is the all-in-one command. For more granular control, use the individual |
run_converge | Iterative coverage: runs the full baseline suite, then automatically runs follow-up rounds targeting coverage gaps and failed scenarios until pass rate and gap thresholds are met (or max rounds reache |
get_context | Retrieve the most relevant source files for a given feature or route. Returns actual source code (budget-capped) so you understand real field names, API endpoints, and component structure before writi |
cleanup | Close all open browsers and reset the session state. Call when done testing. |
configure | Idempotently configure a project and detect its framework, running server, and authentication method. Existing VIBE.md and vibe.config.json files are preserved. |
Read live from the server on October 27, 2026.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/vibe-testing)Nothing comparable is listed yet.
v0.5.0Release notesv0.4.6vibe-testing 0.4.6Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "vibe-testing" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.