Skip to main content
Glama
Sign In
opsmill

infrahub-mcp

Official
by opsmill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to infrahub-mcp

No user-submitted related servers found.

    Related Servers

    • @prismatic-io/prism-mcp by prismatic-io

      @prismatic-io/prism-mcpofficial

      prismatic-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage Prismatic integrations, components, and flows via the Model Context Protocol, supporting code-native integration development and component lifecycle.
      138 npm
      27
      MIT

    • Woodpecker CI MCP Server

      kruyvanna
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to debug pipeline failures, analyze build logs, troubleshoot CI/CD configurations, and manage pipelines and repositories through the Model Context Protocol.
      MIT

    • github-mcp

      fleXRPL
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with GitHub repositories, issues, pull requests, and content via the Model Context Protocol.
      1
      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 12 tools

    Disambiguation5/5

    Each tool targets a distinct action and the descriptions explicitly route between the potentially overlapping ones (get_nodes vs. search_nodes vs. query_graphql; node_upsert vs. mutate_graphql). Read-only vs. write tools are cleanly separated, with clear escalation guidance to GraphQL for complex cases. find_paths and find_reachable are also clearly differentiated (connectivity vs. impact analysis).

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_nodes, search_nodes, get_schema, find_paths, propose_changes, reset_session_branch), and the verbs are semantically meaningful. However node_upsert and node_delete invert the order (noun_verb), creating a minor inconsistency in an otherwise predictable scheme.

    Tool Count5/5

    Twelve tools is well within a comfortable range and each maps to a real need: schema discovery, three read paths, two graph traversals, three write paths, change proposal, and session management. No tool feels redundant or filler.

    Completeness4/5

    The surface covers the full lifecycle — discover schema, read, traverse, write, and open a proposed change — with session handling for branch isolation. Minor gaps remain: no way to list or inspect existing proposed changes, no explicit discard/delete of a session branch (reset only clears the cache), and relationship writes require dropping to raw GraphQL.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources