QA MCP (Probably will rename to vibecheck?)

Created By
Ilikepizza2a year ago
[MCP Server] Complete QA for cursor -> (soon to be renamed to VibeCheck)
Overview

What is QA MCP?

QA MCP is an AI-powered agent designed to streamline web testing workflows, particularly for developers using AI coding assistants like GitHub Copilot. It automates test recording, execution, and discovery using natural language prompts, addressing the challenges of manual testing.

How to use QA MCP?

To use QA MCP, integrate it with your AI coding assistant and interact using natural language commands to record tests, execute existing tests, or discover potential test steps.

Key features of QA MCP?

  • MCP Integration: Seamlessly integrates with AI coding assistants.
  • AI-Assisted Test Recording: Generate Playwright-based test scripts from natural language descriptions.
  • Deterministic Test Execution: Run recorded JSON test files reliably.
  • AI-Powered Test Discovery: Suggest test steps for discovered pages.
  • Regression Testing: Easily run existing test suites to catch regressions.
  • Automated Feedback Loop: Provides direct feedback to the AI assistant.

Use cases of QA MCP?

  1. Automating web application testing after code generation.
  2. Running regression tests to ensure new code changes do not break existing functionality.
  3. Discovering potential test steps for web pages using AI.

FAQ from QA MCP?

  • Can QA MCP work with any AI coding assistant?

Yes! QA MCP is designed to integrate with any AI coding assistant that supports MCP.

  • Is QA MCP free to use?

Yes! QA MCP is open-source and free to use.

  • What programming language is QA MCP built with?

QA MCP is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Ilikepizza2
Star
10
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago