Runtime access
Connections hold credentials, defaults, scopes, and command-family guardrails for external systems.
Integrations
Integrations
OpsRabbit integrations are not just logos. They define how agents receive signals, gather evidence, execute bounded checks, call approved tools, and keep tenant-specific operational data inside access and approval controls.
What this page covers
Use inbounds for signal intake, connections for authenticated runtime commands, and MCP servers for approved tool catalogs.
Use observability, cloud, ITSM, CI/CD, data, code, and custom connectors to reduce manual context gathering.
Use command families, assigned agents, grants, approvals, and sandboxing to control what each integration can do.
Operational detail
How OpsRabbit supports Integrations
OpsRabbit integrations are not just logos. They define how agents receive signals, gather evidence, execute bounded checks, call approved tools, and keep tenant-specific operational data inside access and approval controls.
Tool catalogs
MCP servers expose approved external tools to assigned agents with cached metadata, RBAC, OAuth, and approvals.
Signal flow
Inbounds turn external alerts, incidents, messages, tickets, and calls into assigned investigation threads.
Related pages