1. Conduid
  2. Developer Tools
  3. Vibetest Use
MCP server · Developer Tools

Vibetest Use

Vibetest MCP - automated QA testing using Browser-Use agents

Unclaimed last commit a year ago claudemcpmcp-serverbrowseragentsdevtoolscursor
73Good

Scored 5 months ago · breakdown

About Vibetest Use

Vibetest Use is an MCP server published by browser-use in the Developer Tools category: vibetest MCP - automated QA testing using Browser-Use agents.

The repository has 832 stars and 84 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/browser-use/vibetest-use

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Vibetest Use

Powered by Claude · Grounded in docs

I know everything about Vibetest Use. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 10 hours ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • !Dependencies pinnedNo lockfile. Installs can pull different code over time.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Vibetest Use

Automated QA testing using Browser-Use agents.

https://github.com/user-attachments/assets/9558d051-78bc-45fd-8694-9ac80eaf9494

An MCP server that launches multiple Browser-Use agents to test a vibe-coded website for UI bugs, broken links, accessibility issues, and other technical problems.

Perfect for testing both live websites and localhost development sites.

Vibecode and vibetest until your website works.

Quick Start

# Install dependencies
uv venv
source .venv/bin/activate
uv pip install -e .

# Install the browser
playwright install chromium --with-deps --no-shell

1) Claude Code

# Add MCP server via CLI
claude mcp add vibetest /full/path/to/vibetest-use/.venv/bin/vibetest-mcp -e GOOGLE_API_KEY="your_api_key"

# Test in Claude Code
> claude

> /mcp 
  ⎿  MCP Server Status

     • vibetest: connected

2) Cursor (manually)

  1. Install via MCP Settings UI:
    • Open Cursor Settings
    • Click on "MCP" in the left sidebar
    • Click "Add Server" or the "+" button
    • Manually edit config:
{
  "mcpServers": {
    "vibetest": {
      "command": "/full/path/to/vibetest-use/.venv/bin/vibetest-mcp",
      "env": {
        "GOOGLE_API_KEY": "your_api_key"
      }
    }
  }
}

Basic Prompts

> Vibetest my website with 5 agents: browser-use.com
> Run vibetest on localhost:3000
> Run a headless vibetest on localhost:8080 with 10 agents

Parameters You Can Specify

  • URL: Any website (https://example.com, localhost:3000, http://dev.mysite.com)
  • Number of agents: 3 (default), 5 agents, 2 agents - more agents = more thorough testing
  • Headless mode: non-headless (default) or headless

Requirements

  • Python 3.11+
  • Google API key (get one) (we support gemini-2.0-flash)
  • Cursor/Claude with MCP support

Full Demo

https://github.com/user-attachments/assets/6450b5b7-10e5-4019-82a4-6d726dbfbe1f

License

MIT


Powered by Browser Use

README fetched from the repository 10 hours ago. The original is authoritative.

Questions

About Vibetest Use

How do I install Vibetest Use?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Vibetest Use safe to use with an AI agent?

Its trust score is 73 out of 100 (good). It passes 2 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Vibetest Use still maintained?

The last commit was a year ago and 3 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.