# Vibe Testing MCP server

> Run code-aware Playwright browser tests from your editor, with regression tracking between runs and HTML reports.

- Listing: https://mcp.tc/i/vibe-testing
- Connect: this is a local (stdio) server; install it on your machine (see Install). The listing link is a page, not an MCP endpoint.
- Type: local (stdio)
- Auth: no API key needed
- Category: [Browser Automation](https://mcp.tc/c/browser-automation)
- Vendor: AishwaryShrivastav
- Homepage: <https://vibetesting.tfgstudio.com/>
- Repository: <https://github.com/AishwaryShrivastav/vibe-testing>
- Package: npm `vibe-testing`

## About

Vibe Testing is a local MCP server that gives AI coding editors 14 browser testing tools. It scans your codebase for real routes and form fields, runs scenarios in a Playwright browser, and compares each run with the previous one to report fixes and regressions. It also produces HTML reports with screenshots, API activity and reproduction steps.

It runs locally over stdio with npx -y vibe-testing@latest --mcp and needs Node.js 20+ and Playwright Chromium. No API key or sign-in is needed, and the tool makes no LLM calls itself. An init command can register it in Claude Code, Cursor, Windsurf, VS Code Copilot and Roo Code.

## What it can do

- Scan a codebase to find routes, forms and field names
- Run test scenarios in a real Playwright browser
- Log in to the app under test with test credentials
- Explore pages and execute generated scenarios
- Diff each run against the last to show fixes and regressions
- Generate HTML reports with screenshots and API activity

## Example prompts

- "Scan this codebase and test it against http://localhost:3000"
- "Test the checkout flow and show me what broke"
- "Run a full test and tell me what my last change regressed"
- "Generate a QA report with screenshots for the login flow"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport stdio vibe-testing -- npx -y vibe-testing
```

2. Start Claude Code and type `/mcp`. **vibe-testing** should show as connected.

Add `--scope user` to make it available in every project.

### Claude Desktop

1. Open **Settings → Developer → Edit Config**. It opens `claude_desktop_config.json`. Add:

`claude_desktop_config.json`:

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

2. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in `~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on Windows.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=vibe-testing&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsInZpYmUtdGVzdGluZyJdfQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

Needs Node.js on your computer.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=vibe-testing&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22vibe-testing%22%5D%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"vibe-testing","type":"stdio","command":"npx","args":["-y","vibe-testing"]}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

Needs Node.js on your computer.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

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

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

### Codex

```bash
codex mcp add vibe-testing -- npx -y vibe-testing
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

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

Needs Node.js on your computer.

### Gemini CLI

```bash
gemini mcp add vibe-testing npx -- -y vibe-testing
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under `context_servers` in its settings, with the same `command`, `args` and `env` fields.

Needs Node.js on your computer.

## Recent changes

- 2026-11-14 08:27 UTC: New version 0.5.0 (was 0.4.6), read from npm. Source: automatic check.
- 2026-10-27 11:36 UTC: Tracking started: version 0.4.6. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/vibe-testing#history (Atom feed: https://mcp.tc/i/vibe-testing/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.5.0
- Last checked: 2026-10-27
- Listed: 2026-10-27
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/vibe-testing (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
