Design choice
Choose connection for credentials and commands, plugin for packaged behavior, MCP for tool catalogs, workflow for deterministic process.
Custom connectors cover systems that do not fit a built-in provider. Teams can use custom connection targets, APIs, plugins, MCP servers, workflows, or source inbounds to bring proprietary operational context into OpsRabbit.

What this page covers
Use Custom connections for bounded command or API access when provider-specific forms do not exist.
Use plugins for packaged tools, widgets, channel integrations, scheduled work, and customer-owned context collection.
Use MCP servers or workflows when a third-party tool catalog or deterministic procedure is a better fit.
Operational detail
Custom connectors cover systems that do not fit a built-in provider. Teams can use custom connection targets, APIs, plugins, MCP servers, workflows, or source inbounds to bring proprietary operational context into OpsRabbit.
Choose connection for credentials and commands, plugin for packaged behavior, MCP for tool catalogs, workflow for deterministic process.
Classify plugin code by trust tier and keep third-party or unreviewed capabilities behind runner execution and approvals.
Custom extensions that save operational data should store and filter records by tenant id in MSP deployments.
Related pages