Vibe Test — Browser Testing Agent
Run code-aware browser tests from your AI editor with 13 Playwright MCP tools instead of hand-writing every E2E step.
Overview
Vibe Test is an MCP server for the Ship phase that provides 13 Playwright tools for code-aware browser testing in AI editors.
What is this MCP server?
- 13 Playwright tools exposed via MCP for AI code editors
- Code-aware browser testing agent (npm package vibe-testing, stdio transport)
- Registry version 0.4.2 on npm
- Designed for MCP clients that drive real browser sessions
- GitHub: AishwaryShrivastav/vibe-testing
- Package version 0.4.2
- Transport: stdio via npm registryType vibe-testing
Community signal: 4 GitHub stars.
What problem does it solve?
Solo builders struggle to keep E2E coverage aligned with rapid AI-generated UI changes without constant context switching to Playwright scripts.
Who is it for?
Builders using Cursor or Claude Code who ship web frontends and want agent-driven Playwright checks locally.
Skip if: Backend-only APIs with no browser surface, or teams that need enterprise CI orchestration instead of editor-integrated MCP tools.
What do I get? / Deliverables
Your agent can drive real browser tests through MCP so UI regressions surface during Ship before users do.
- Agent-invoked browser test runs via 13 MCP Playwright tools
- Faster UI validation loops before release
Recommended MCP Servers
Journey fit
Browser automation MCP belongs in Ship because solo builders validate UI flows and regressions right before release. Testing is the canonical shelf: Vibe Test exposes Playwright-driven browser actions for automated checks, not production monitoring.
How it compares
Playwright MCP tooling for editors, not a replacement for full pipeline CI or static analysis skills.
Common Questions / FAQ
Who is Vibe Test for?
Solo and indie developers who use AI code editors and need Playwright-based browser testing wired through MCP.
When should I use Vibe Test?
Use it in Ship/testing when you want the agent to run or refine browser tests against your app before launch.
How do I add Vibe Test to my agent?
Install the npm package vibe-testing (0.4.2), configure stdio MCP in your client, and point the server entry to the published vibe-testing identifier per the repo README.