Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to SmartBear MCP server

No user-submitted related servers found.

    Related Servers

    • SmartBear MCP

      keybrdist
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with seamless access to SmartBear's suite of testing and monitoring tools, enabling querying testing data, analyzing performance metrics, and managing test automation through natural language.
      12,105 npm
      MIT

    • @checked/mcp

      Laozofficial
      A
      license
      B
      quality
      C
      maintenance
      Lets AI assistants inspect test run results, AI QA reports, and findings with their full evidence, and, when asked, start runs, re-run only failed tests, import API specs, or scan a website. Read-only tools are free, while work-starting tools consume the workspace's allowance and report usage limits.
      19
      22 npm
      MIT
    • Sauce Labs MCP Server

      Sauce Labs MCP Serverofficial

      saucelabs
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with Sauce Labs testing platform through natural language, providing access to device cloud management, test job analysis, build monitoring, and testing infrastructure insights. Supports both Virtual Device Cloud (VDC) and Real Device Cloud (RDC) with comprehensive test analytics and team collaboration features.
      34
      10
      Apache 2.0

    • LogicMonitor MCP Server

      EddyAOrtiz
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to query and manage monitoring data through structured tools, covering alerts, devices, metrics, dashboards, reports, remediation workflows, and optional AI/ML analysis integrations.
      -
    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

    C2.8/5.0

    Scored across 316 tools

    Disambiguation2/5

    Despite product prefixes, the set contains many near-duplicate surfaces: qmetry_fetch_test_cases vs qmetry_fetch_test_case_details, three different tools returning Test Run UDFs (fetch_test_run_udf_values, fetch_test_case_runs_by_test_suite_run, fetch_test_case_executions), multiple linked-issue/linked-requirement variants, and parallel test-case CRUD in QMetry, QTM4J, and Zephyr. Several descriptions even contain explicit 'do NOT use this tool for X, use Y instead' warnings and catch-all escape hatches (bearq_chat_with_qa_lead, collaborator_reviewservice_action), which is direct evidence of ambiguous boundaries.

    Naming Consistency3/5

    Most tools follow a product-prefix + verb_noun pattern (qmetry_create_test_case, zephyr_get_test_cycle, bugsnag_list_projects). However prefixes mix hyphenated (contract-testing_) with underscored, and some names contain embedded hyphens (contract-testing_get_bdct_cross-contract_verification_results, get_bdct_x-contract_test_results_by_consumer), plus inconsistent verb styles within QMetry (fetch_ vs get_ vs list_, e.g. fetch_test_case_details vs list_projects) and noun-style collaborators like reviewservice_action. Readable overall but clearly not one convention.

    Tool Count1/5

    316 tools is an extreme overshoot for any single MCP server; even granting that it aggregates nine SmartBear products, the count is far beyond the 3-15 sweet spot and beyond what an agent can reliably select from. Many tools are narrow admin or pagination variants (e.g., dozens of contract-testing admin/role/team tools, three QMetry project-info tools) that bloat the surface.

    Completeness4/5

    Coverage per domain is unusually thorough: full create/read/update/link/unlink lifecycles for test cases, suites, cycles, requirements, issues, and executions in QMetry/QTM4J, plus PactFlow contract publishing, environments, deployments, webhooks, and Swagger portal/API management. Minor gaps exist (e.g., Zephyr lacks delete operations for most entities, and some escape hatches cover missing lifecycle actions), but overall the surface is broad and rarely dead-ends.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling

    Resources