Vibetest Use MCP
An MCP server that spins up several browser agents to test a site for broken links, UI bugs and accessibility issues
- 836 ★ on the repository
- Last commit
Extended access
Why this level
- Drives a real browser and navigates sites
- Sends page data to the Gemini model
Install
- Works in
Manual install
claude mcp add vibetest /full/path/to/vibetest-use/.venv/bin/vibetest-mcp -e GOOGLE_API_KEY="your_api_key"First run: uv venv, uv pip install -e ., playwright install chromium.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Drives a real browser and navigates sites
- Sends page data to the Gemini model
This is third-party code. Review the repository files before installing.
What it does
Vibetest runs an MCP server that, on a single command, launches a group of Browser Use agents and sends them across a given site. The agents look for UI defects, broken links, accessibility problems and other technical issues, then collect the findings into a report. It works on both a live site and local development on localhost. The request sets the URL, the number of agents and the window mode, headless or visible. The server connects to Claude Code and Cursor.
Who it is for. For developers and QA engineers who want a quick agent-driven pass over a site.
Good fit when
- You want a quick site pass for broken links and UI defects
- You want to test a local build on localhost before publishing
- You want to parallelize the check across several agents
Not a fit when
- You need a deterministic test suite with fixed scenarios
- You have no Google API key or access to the Gemini model
Example request
Run vibetest on localhost:3000 with five agents and collect a reportMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
GOOGLE_API_KEYrequired, secret- Google API key for the gemini-2.0-flash model
Limitations
It needs a Google API key and runs on the gemini-2.0-flash model. It requires Python 3.11 and a Chromium install via playwright. Installation is from source with uv; there is no published registry package. Agent checks are non-deterministic, so results vary between runs.
How to disable. Remove the vibetest entry from the agent's MCP configuration and delete the project's local environment.
FAQ
Can it test a local site?
Yes, the server works with both a public URL and localhost, for example localhost:3000 or localhost:8080.
Why multiple agents?
The user sets the agent count, default three; more agents give a broader pass in a single run.
Discussion
No questions or reviews yet.
Related
MCP serversBrowserStack MCP Server: testing on real devices
BrowserStack MCP Server
The official BrowserStack MCP server: real devices, automated tests and test cases driven by an agent from your editor
One binary for agent browser automation: a CLI with browser and check skills, an MCP server and clients for JS, Python and Java
kogiQA MCP gives an agent a browser that finds page elements without selectors, for debugging web apps and writing e2e tests
MCP server, agent and skills for end-to-end UI tests where the agent drives the computer through vision on cloud machines
MCP server: an agent sends GET, POST, PUT, DELETE and PATCH to your REST API and gets back status, headers and body
The SmartBear server gives the agent BugSnag, Swagger, Zephyr, QMetry and PactFlow: errors, API specs, test cases and contracts
README in short
The README presents Vibetest as an MCP server for automated agent-driven QA of a site with Browser Use agents. Installation uses uv with an editable package install and a Chromium download for playwright. For Claude Code the server is added with claude mcp add and a Google API key, for Cursor through the MCP settings. The request sets the URL, agent count and headless mode. It needs Python 3.11 and a Google API key for the gemini-2.0-flash model. MIT licensed.