A
licenseA
qualityC
maintenanceAI-native browser testing, directly from your coding agent.
3
MIT
Debugg AI MCP
Officialby debugg-ai
Related Servers
Alternatives to Debugg AI MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnd-to-end AI test generation and QA automation server that orchestrates auto-detection, browser exploration, test generation, execution, and dashboard analysis directly from your IDE.1-
- AlicenseNot gradedqualityDmaintenanceAutonomous QA platform powered by Claude + Playwright that allows AI to write, run, and fix tests for any project.MIT
- AlicenseAqualityDmaintenanceRun real Playwright E2E tests from your AI coding agent.413 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to generate, score, run, and auto-heal Playwright E2E tests while enforcing domain-driven page object architecture and anti-flakiness rules.-
- AlicenseAqualityBmaintenanceEnables AI assistants to create, run, autocorrect, and monitor Playwright tests for your app with a local dashboard, credential vault, and public status page.16MIT
TDQS
A4.3/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct function: quick render probes, interactive browser verification, knowledge-graph crawling, environment/credential management, execution history, project management, and test case/suite management. probe_page and check_app_in_browser are explicitly differentiated with WHEN TO USE/NOT FOR guidance, so an agent should not misselect.
Naming Consistency3/5
Names mix styles: verb_noun action tools (probe_page, check_app_in_browser, trigger_crawl) alongside bare-noun resource managers (environment, executions, project) and compound resource nouns (test_case, test_suite). The pattern is readable and the action-parameter convention is consistent, but the naming itself is not uniform.
Tool Count5/5
8 tools is a well-scoped set for a browser QA/testing platform. Each tool covers a distinct workflow area without redundancy, and the count is neither thin nor bloated.
Completeness4/5
Core workflows are covered: projects, environments, suites, test cases, execution history, browser checks, and crawls. Minor gaps exist — project has no update/delete in the tool, and test_case lacks a list/get action — but these are workaroundable via the web app or suite results and don't create dead ends.
Maintenance
ActivityActive
ResponsivenessNo issues