Skip to main content
Glama
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.
      122 npm
      26
      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 clearly distinct action or resource: reads (get_nodes, search_nodes, query_graphql), graph analysis (find_paths, find_reachable), writes (node_upsert, node_delete, mutate_graphql), schema discovery (get_schema), and session/branch workflow (get_session_info, reset_session_branch, propose_changes). Descriptions explicitly clarify boundaries, such as when to prefer get_nodes/search_nodes over query_graphql and when to use node_upsert versus mutate_graphql.

    Naming Consistency4/5

    Most tools follow a snake_case verb_noun pattern (query_graphql, get_nodes, search_nodes, find_paths, propose_changes, reset_session_branch). A few deviate with noun_verb ordering (node_upsert, node_delete) and a slightly shortened form (find_reachable), but the overall naming remains predictable and readable.

    Tool Count5/5

    The 12 tools are well-scoped for a graph data platform that requires reads, writes, traversal, schema discovery, and branch/session management. Each tool has a clear role, and the set avoids both thinness and bloat.

    Completeness4/5

    Core lifecycle operations are covered: schema discovery, typed and GraphQL reads, graph traversal, node upsert/delete, complex mutations, session branch switching, and proposing changes. Minor gaps exist around the proposed-change lifecycle after creation, such as listing, inspecting, merging, or closing proposed changes.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources