Infrahub Source of Truth

Infrahub Source of Truth

MCP Server

• Repository: opsmill/infrahub-mcp
• Version: 1.1.7+ (reworked — first stable release + production hardening)
• Distribution: PyPI (pip install infrahub-mcp), Docker (registry.opsmill.io/opsmill/infrahub-mcp), or from source
• Entry point: infrahub-mcp console script
• Transport: stdio (default) or streamable-http (remote clients / auth modes)
• Requires: INFRAHUB_ADDRESS + (INFRAHUB_API_TOKEN or INFRAHUB_USERNAME+INFRAHUB_PASSWORD)
• Python: 3.13+
• Dependencies: fastmcp>=3.2.0, infrahub-sdk>=1.20.0
• Docs: docs.infrahub.app/mcp (per-client setup, auth, configuration)

What changed in the rework: the server moved to a modular src/infrahub_mcp/ layout on FastMCP 3.x, added a branch-isolated write model (writes never touch the default branch), exposes MCP resources and prompts in addition to tools, serializes schema output with TOON internally to cut tokens, and ships as a PyPI package + Docker image with optional auth, rate limiting, caching, and OpenTelemetry/Prometheus observability. The old read-only tool surface (get_node_filters, get_related_nodes, get_schema_mapping, get_schemas, get_graphql_schema, get_branches, branch_create) has been replaced — see the table below.

How Infrahub Differs

Infrahub is not just another IPAM/DCIM tool. Key differentiators:

• Schema-driven — define your own infrastructure models (not just built-in IPAM/DCIM). Devices, circuits, IP addresses, services, cloud resources — any infrastructure object can be modeled.
• Versioned branches — Git-like branching for infrastructure data. Changes are made on a branch, reviewed as a diff, and merged when approved. No more "who changed this in production?"
• GraphQL-native — full GraphQL API for flexible queries, not just REST. Query exactly the fields you need, traverse relationships in a single request.
• Relationship-first — rich relationship model between objects with relationship-level filters and traversal.

Safety Model: Branch-Isolated Writes

The reworked server makes destructive operations safe by construction:

• Writes never hit the default branch. On the first write in a session, the server lazily auto-creates a session branch named mcp/session-YYYYMMDD-<hex> (pattern configurable via INFRAHUB_MCP_BRANCH_PATTERN). All node_upsert / node_delete / mutate_graphql land there.
• Human review is mandatory to merge. propose_changes opens a Proposed Change (PR) from the session branch to the default branch — a human reviews and merges it in the Infrahub UI. The