Skip to main content
Glama
shahinnr

qa-mcp

by shahinnr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to qa-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • qa-mcp

      davidpoza
      A
      license
      C
      quality
      B
      maintenance
      Automates generation of QA artifacts such as API tests, E2E tests, and documentation exports. It supports REST Assured, Cypress, and Excel/Word document generation.
      5
      1 npm
      MIT

    • TestAtlas

      Karzone
      A
      license
      A
      quality
      A
      maintenance
      Turn any .NET test-automation solution into a queryable map in one SQLite file — features, steps, API clients, page objects, and their dependencies. Zero config, no AI, no network, 100% deterministic.
      4
      11
      3
      MIT

    • Argus

      chriswu727
      A
      license
      A
      quality
      A
      maintenance
      AI-powered exploratory QA agent. Explores web apps like a real user — 18 MCP tools for clicking, filling forms, and navigating. Automatically verifies that actions persist (fake deletes, failed edits). Runs 16 detection types including dead links, SEO, accessibility, and performance checks.
      29
      2
      MIT

    • AutoDev MCP

      rookiejefren
      F
      license
      Not graded
      quality
      D
      maintenance
      A dual-track testing server that combines CLI test execution with Playwright-based browser testing and persistent SQLite logging. It enables automated test pipelines, Git integration, and evidence-based requirement generation to streamline the development lifecycle.
      -
    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.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct task: discovery, API tests, UI tests, flow tests, combined run, report reading, and diffing. There is no overlap in their purposes, and descriptions clearly delineate their roles.

    Naming Consistency5/5

    All tools use a consistent qa_ prefix followed by a clear verb (discover, run_flows, run_api, run_ui, run_all, report, diff). The pattern is uniform and predictable, making it easy to infer tool functions from names.

    Tool Count5/5

    Seven tools is well within the ideal range for a QA-focused server. Each tool covers a necessary step in the workflow without redundancy or bloat, making the set tightly scoped.

    Completeness5/5

    The tool surface covers the full QA lifecycle: discovering testable surface (qa_discover), executing different test types (flows, API, UI), running all together (qa_run_all), and then analyzing results via qa_report and qa_diff. There are no obvious dead ends or missing operations for the server's purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources