Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vibe-test": {
"args": [
"-y",
"vibe-testing@latest",
"--mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Code-aware browser testing agent for AI-powered editors.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'vibe-testing' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked vibe-testing against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser
Browser automation with Puppeteer for web scraping and testing
Self-hosted URL- and file-to-Markdown service for humans and AI agents - web pages, documents, images, audio, YouTube. PWA + REST + MCP + Claude Code skill, Reddit-aware, refreshable share links.
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for io.github.AishwaryShrivastav/vibe-testing and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Code-aware browser testing agent for AI-powered editors.
Reads your codebase, understands every route and form, opens a real Playwright browser, explores every element, and reports what works and what breaks — with screenshots.
Works as an MCP server that gives your AI editor (Claude Code, Cursor, Windsurf, VS Code Copilot) 13 browser testing tools — or as a standalone CLI.
cd /path/to/your/project
npx vibe-testing@latest init
This command:
~/.claude/settings.json, ~/.cursor/mcp.json, etc.) 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.jsonThen open your editor and say:
"Scan this codebase and test it against http://localhost:3000"
Your AI will pick up the tools automatically and start testing.
npx vibe-testing@latest init
↓
Registers 13 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 step
No 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.
npx vibe-testing@latest init
Detects and configures all installed editors. Done.
Add to ~/.claude/settings.json (global — works in every project):
{
"mcpServers": {
"vibe-test": {
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}
Or add to .mcp.json in your project root (project-level only):
{
"mcpServers": {
"vibe-test": {
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}
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": {
"command": "npx",
"args": ["-y", "vibe-testing@latest", "--mcp"]
}
}
}
Add to .roo/mcp.json:
{
"mcpServers": {
"vibe-test": {
"command": "np
... [View full README on GitHub](https://github.com/aishwaryshrivastav/vibe-testing#readme)