MCP Tools Directory
← Browse integrations

Developer tools

com.opsmill/infrahub-mcp

Free account · sign-in required

Contact com.opsmill/infrahub-mcp

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

An MCP server connects your AI assistants to Infrahub using the open MCP standard.

Transport
stdio
Authentication
api-key
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
0.1.2
Package
infrahub-mcp
Last compatibility test
Not independently tested

Connect your agent

infrahub-mcp

Pinned publisher README and Python manifest reviewed. Eligibility is documented only; the package and Infrahub service were not executed or independently security-audited. The publisher states that writes use session branches and require human approval before merging, but arbitrary GraphQL operations retain the configured token's permissions.

Capabilities: Query Infrahub infrastructure data, Explore schemas and GraphQL resources, Create branch-isolated changes, Propose changes for human review, Run GraphQL queries and mutations

Connected profiles

Additional details

Registry identifier

com.opsmill/infrahub-mcp

Source ↗ · Checked 2026-09-17
Published version

0.1.2

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

pypi

Source ↗ · Checked 2026-09-17
Required configuration names

INFRAHUB_ADDRESS, INFRAHUB_API_TOKEN

Source ↗ · Checked 2026-09-17
Source artifact

infrahub-mcp

Source ↗ · Checked 2026-09-19
Source manifest version

1.1.8

Source ↗ · Checked 2026-09-19
Unattended configuration

The publisher documents environment-based configuration and direct console-script startup, with stdio as the default transport for desktop and IDE clients; this review did not execute it.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

The reviewed configuration requires the Infrahub service address and an Infrahub API token supplied through environment variables.

Source ↗ · Checked 2026-09-19
Connection configuration

The publisher explicitly documents stdio as the default client transport and a separate opt-in streamable HTTP command; this approval covers the existing stdio listing only.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19