Skip to main content
Glama
Sign In
openqa-mcp

openqa-mcp

by mimi1vx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to openqa-mcp

No user-submitted related servers found.

    Related Servers

    • vyos-mcp

      Galvill
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing VyOS appliances through their HTTP API, providing tools for configuration, operational commands, and interactive troubleshooting.
      MIT

    • garmonia-crm-mcp

      AlekseiKastsiuk
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables testing and interacting with the Garmonia hotel CRM through its internal API, including orders, clients, brands, calendar, and general CRUD operations via an authenticated session.
      -

    • Opus MCP Server

      Moenamatics
      A
      license
      A
      quality
      D
      maintenance
      Enables programmatic interaction with Opus workflow automation platform, allowing users to initiate jobs, execute workflows, monitor status, upload files, and retrieve results through the Opus Job Operator API.
      7
      MIT

    • hydra-mcp

      slopinger
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to inspect and manage the Nix CI server's projects, jobsets, evaluations, builds, build steps, logs, and queue across multiple instances, and with credentials trigger evaluations, restart or cancel or bump builds, and create or edit projects and jobsets.
      18
      MIT

    • mcp-xray

      Mammals-at-work
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Xray Cloud and Data Center for test management, including authentication, GraphQL queries, test execution/plan management, and result import via MCP.
      9
      5 npm
      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

    C2.8/5.0

    Scored across 40 tools

    Disambiguation4/5

    Tools are generally distinct, targeting specific resources and actions. However, list_jobs and list_jobs_overview serve similar purposes with different output detail, and find_jobs_by_setting overlaps with list_jobs filtering, causing slight ambiguity.

    Naming Consistency4/5

    All tools use snake_case with a verb-first pattern (e.g., delete_job, list_machines). A few exceptions like find_jobs_by_setting and list_jobs_overview deviate slightly but remain consistent in style.

    Tool Count3/5

    40 tools is relatively high for an MCP server, indicating a broad scope. While each tool serves a specific function, the count may be overwhelming for simple use cases, though justified for a full-featured openQA client.

    Completeness4/5

    The tool surface covers major operations for jobs, groups, comments, assets, and scheduling. Minor gaps exist, such as missing update/delete for bugs and direct job creation, but core workflows are well-supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources