Skip to main content
Glama
galkremer1

cnv-lab-mcp

by galkremer1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to cnv-lab-mcp

No user-submitted related servers found.

    Related Servers

    • racksmith

      Amiirhosseini
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for bare-metal lab operations, enabling inventory, commissioning, deployment, fabric audit, and job scheduling via Hermes agent skills and a tool server.
      Apache 2.0

    • techzone-mcp

      zm-gh-ibm
      F
      license
      A
      quality
      B
      maintenance
      MCP server for IBM Technology Zone: manage reservations end-to-end and search the catalog from Claude.
      11
      -

    • GLPI MCP Server v2

      Luizcc87
      A
      license
      C
      quality
      A
      maintenance
      MCP server for GLPI integration, providing tools for ITIL management (tickets, problems, changes, knowledge base, stats, assets, and administration) via the GLPI API.
      30
      MIT

    • quads-mcp

      grafuls
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct resource-action targets, but a few boundaries could be sharper: check_availability and find_available_cluster both deal with availability, and get_cluster_info vs. get_cluster_kubeconfig both extract from the same deploy artifact. Descriptions clarify the difference well enough that an agent can usually choose correctly.

    Naming Consistency5/5

    All 15 tool names follow a consistent snake_case verb_noun convention (list, check, find, reserve, cancel, trigger, get, abort, import, plan, execute). There are no camelCase names, vague single verbs, or arbitrary suffixes.

    Tool Count5/5

    Fifteen tools is at the upper end of the ideal range but appropriate for the server's scope: reservation management, Jenkins build control, cluster artifact access, ACM import/monitoring, and scenario orchestration. Each tool covers a distinct step and no tool feels redundant.

    Completeness3/5

    The core path from finding/reserving assets, triggering and monitoring builds, extracting cluster credentials, and importing a spoke into ACM is covered. However, the lifecycle lacks cleanup operations (e.g., deleting/detaching a ManagedCluster, removing an imported spoke) and there is no dedicated way to list or look up existing reservations before canceling.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources