Skip to main content
Glama
parajuliminiyan

QA Automation MCP Server

by parajuliminiyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to QA Automation MCP Server

No user-submitted related servers found.

    Related Servers

    • ProdPoke MCP Server by prodpoke

      ProdPoke MCP Serverofficial

      prodpoke
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to perform real-browser QA testing on websites via Playwright, finding bugs, accessibility, SEO, and performance issues through natural language conversations.
      1
      MIT

    • QAcito

      dpaul20
      A
      license
      Not graded
      quality
      B
      maintenance
      Autonomous QA platform powered by Claude + Playwright that allows AI to write, run, and fix tests for any project.
      MIT

    • qa-ai-agents

      abchahal
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables automated QA testing by running a pipeline of AI agents that generate test scenarios, architect test layers, write Playwright tests, and review code, all grounded in feature requirements and API contracts.
      -

    • tuxedo-qa

      jonathan-ponciano
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to create, run, autocorrect, and monitor Playwright tests for your app with a local dashboard, credential vault, and public status page.
      16
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose: crawl_page extracts elements, write_test generates tests, run_test executes them. No overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case: crawl_page, write_test, run_test. Predictable and clean.

    Tool Count5/5

    Three tools perfectly cover the core workflow of a QA automation server: crawl, write, run. Not excessive, not insufficient.

    Completeness4/5

    The essential workflow is complete, but missing test management tools (e.g., delete, list) or debugging utilities. Minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources