Integrations

    MCP Servers

    MCP servers connect OpsRabbit agents to approved external tool catalogs. Admins register servers, store credentials, refresh tool metadata, and assign servers to the agents that may discover and call them at runtime.

    MCP Servers social preview image

    What this page covers

    Support stdio, streamable HTTP, and SSE transports with none, bearer token, or OAuth authentication.

    Agents receive a compact MCP gateway and should search or describe available tools before calling them.

    Runtime calls require the server to be enabled, assigned to the agent, allowed by access policy, and approved when policy requires it.

    Operational detail

    How OpsRabbit supports MCP Servers

    MCP servers connect OpsRabbit agents to approved external tool catalogs. Admins register servers, store credentials, refresh tool metadata, and assign servers to the agents that may discover and call them at runtime.

    Metadata control

    Tool metadata is cached so agents can search catalogs without loading large schemas into every prompt turn.

    Access model

    Read access can inspect metadata; use access is required to call tools or read exposed MCP resources.

    Approval posture

    Keep destructive tools behind approval and avoid exposing unreviewed third-party MCP servers to production agents.

    Related pages

    More in Integrations