Managing Integrations

The Integrations page connects RubixKube with your existing tools for notifications, metrics, workflows, and agent capabilities.

Integrations page with counters for total, enabled, available, and error state. Rows for Slack, RubixKube Docs, Exa, GitHub, Notion, Atlassian Rovo, Linear, PagerDuty, AWS Knowledge, DeepWiki, and Context7 with protocol and tool badges.

System Integrations

Slack

Get incident notifications in Slack

Setup:

Click “Connect Slack”
Authorize RubixKube app
Select channel for alerts
Configure notification rules

PagerDuty

Page on-call for critical incidents

Setup:

Click “Connect PagerDuty”
Enter integration key
Map severity levels
Test integration

Prometheus

Enhanced metrics collection

Setup:

Enter Prometheus endpoint
Configure scrape interval
Verify connection

Webhooks

Custom integrations

Setup:

Add webhook URL
Select events to trigger
Configure payload format

Notification Rules

Configure when to be notified: - HIGH severity incidents only

All incidents
RCA report completion
Cluster disconnection

Delivery channels: - Slack messages

PagerDuty alerts
Webhook calls
Email (coming soon)

Custom Integrations

Custom Integrations let you connect your own private MCP servers and REST APIs to RubixKube. Once registered, their tools appear automatically alongside system integrations — available to the SRI Agent through Chat, with zero extra plumbing.

Enterprise feature. Custom integrations are available on the Enterprise plan. Free and Pro tenants will see a 403 response.

Two Protocols

Custom integrations support two protocols. Choose based on what you’re connecting:

MCP Server

Connect a private Model Context Protocol server — the same standard used by system integrations. Supports SSE, HTTP, and stdio transports.Best for: MCP-native tools like Linear, GitHub, Notion, or any server that speaks MCP.

REST API

Expose any REST API as agent tools by defining tool schemas and HTTP mappings. No MCP server needed — RubixKube translates tool calls to HTTP requests.Best for: Internal APIs, ticketing systems, CMDB, or any service with a REST endpoint.

Adding an MCP Server

Add Custom Integration dialog showing MCP Server and REST API protocol options with metadata fields

Open Integrations

Navigate to Integrations in the left sidebar.

Click + Add Custom Integration

Select MCP Server as the protocol type.

Fill in Metadata

Field	Description
Name	URL-safe slug (lowercase, numbers, hyphens). Unique per tenant
Display Name	Human-readable name for the integration card
Description	Short description of what this integration does
Logo URL	URL to the integration’s logo/icon
Category	Category for filtering (e.g., `version_control`, `project_management`)

Configure MCP Connection

MCP configuration showing Server URL, Transport, Auth type, and API Token fields

Field	Description
Server URL	Full URL to your MCP server endpoint (e.g., `https://mcp.zapier.com/api/v1/connect`)
Transport	`SSE` (default), `HTTP`, or `stdio`
Auth Type	`Bearer / API Key` (default), `OAuth2`, or `None`
Auth Header Prefix	Prefix for the Authorization header (default `Bearer`, use `Token` for GitHub)
API Token	Your authentication token

You can also use the Edit as JSON panel on the right to configure the integration directly as JSON.

Test Connection

After creation, click Test to verify connectivity. The test negotiates the MCP handshake with the remote server and updates the health status on the card.

Once connected, the integration’s tools appear immediately in the MCP gateway — no restart or config change needed.

Adding a REST API

Add Custom Integration dialog with REST API selected and metadata fields

Select REST API Protocol

Choose REST API as the protocol type when adding a new custom integration.

Enter Metadata

Fill in the metadata fields: Name (slug), Display Name, Description, Logo URL, and Category.

Enter Base URL and Auth

REST API configuration showing Base URL, Auth type, Access token, and Custom headers

Field	Description
Base URL	Base URL of your API (e.g., `https://api.example.com`)
Auth Type	`Bearer token`, `API Key`, `Basic auth`, or `OAuth2`
Access Token	Your authentication token (encrypted at rest)
Custom Headers	Optional static headers merged into every request (click + Add header)

Define Tools

Tools section with Import from OpenAPI and Define manually tabs

You can define tools in two ways:

Import from OpenAPI — upload or paste an OpenAPI 3.x / Swagger 2.0 spec to auto-generate tools
Define manually — click + Add tool to define each tool by hand

Each tool represents one API operation the SRI Agent can invoke:

Field	Description
Name	Tool identifier (e.g., `list_tickets`)
Description	What the tool does — the agent reads this to decide when to use it
HTTP Method	`GET`, `POST`, `PUT`, `PATCH`, or `DELETE`
Path	URL path appended to the base URL (supports path params like `/tickets/{id}`)
Parameters	Query params and body params for the tool

Create and Test

Click Add Integration and then Test to verify connectivity. REST tests probe common health paths (/healthcheck, /healthz, /health, /ping) with your configured auth.

Managing Custom Integrations

Editing a Custom Integration

To update an existing custom integration, click on its card in the catalog and select Edit. The edit form opens pre-populated with all current values.

Open the Integration Card

Find the custom integration in the catalog. Custom integrations are shown in the Custom section below the system integrations.

Click Edit

Click the Edit (pencil) icon on the integration card or in the settings panel.

Update Fields

Modify any metadata or connection settings:

Field	Behavior on Update
Display Name / Description / Logo URL / Category	Updated immediately
Connection settings (URL, transport, etc.)	Replaced on save
Credentials (API token, OAuth config)	Passing new credentials replaces them entirely (re-encrypted). Omit to preserve existing credentials.
Tools	Add, remove, or redefine tool schemas

Save Changes

Click Save to apply. The updated integration takes effect immediately in the MCP gateway.

Other Integration Actions

Disable / Re-enable — Toggle the integration’s status between active and disabled. Disabled integrations are excluded from the MCP gateway. Tool Filtering — Control which tools are available to agents:

Enabled tools — allowlist of specific tool names. Empty means all tools allowed.
Disabled tools — blocklist applied after the allowlist. If a tool appears in both, it’s blocked.

Delete — Permanently removes the integration and all associated credentials. Test Connection — Run a health check at any time. Health status is displayed on the integration card with consecutive failure count and last error.

Authentication

Credentials are passed plaintext on create — the server encrypts them before storing. They are always masked in responses.

MCP — Bearer Token

{
  "auth_type": "bearer",
  "api_token": "your-token-here"
}

MCP — OAuth 2.1 (Authorization Code)

For user-facing OAuth flows (e.g., Atlassian, GitHub):

{
  "auth_type": "oauth2",
  "oauth": {
    "grant_type": "authorization_code",
    "client_id": "your-client-id",
    "client_secret": "your-client-secret",
    "authorization_url": "https://provider.com/oauth/authorize",
    "token_url": "https://provider.com/oauth/token",
    "scope": "read write",
    "use_pkce": true
  }
}

Or with OIDC discovery (auto-discovers endpoints from issuer URL):

{
  "auth_type": "oidc",
  "oauth": {
    "grant_type": "authorization_code",
    "client_id": "your-client-id",
    "issuer_url": "https://auth.provider.com",
    "scope": "openid read:data",
    "use_pkce": true
  }
}

MCP — OAuth 2.1 (Client Credentials)

For server-to-server flows:

{
  "auth_type": "oauth2",
  "oauth": {
    "grant_type": "client_credentials",
    "client_id": "your-client-id",
    "client_secret": "your-client-secret",
    "token_url": "https://provider.com/oauth/token",
    "scope": "api:read api:write"
  }
}

MCP — No Auth

Set auth_type: “none” and omit credentials entirely.

REST — Bearer Token

{ "access_token": "eyJhbGciOi..." }

Also accepts api_token or token.

REST — API Key

{ "api_key": "your-api-key" }

REST — Basic Auth

{ "username": "alice", "password": "s3cr3t" }

OAuth Flows

For OAuth-based integrations, RubixKube handles the full authorization code flow:

Create the Integration

Authorize

Click Authorize on the integration card. This opens the OAuth provider’s consent page in a popup or redirect.

Complete Consent

After you approve, the provider redirects back to RubixKube’s callback endpoint. Tokens are automatically encrypted and stored.

Token Refresh

Token refresh happens automatically during tool calls. You can also manually trigger a refresh from the integration card to verify token health.

OAuth discovery: RubixKube can auto-discover authorization and token URLs from the MCP server’s .well-known/oauth-authorization-server or the standard OIDC .well-known/openid-configuration endpoint.

How Custom Integrations Appear to Agents

Once created, custom integration tools surface automatically in the tenant’s MCP gateway alongside system integration tools:

Tool discovery — custom tools appear in tools/list and discover_tools()
Tool execution — tools/call routes to your server or API with the configured auth
Namespacing — tools are namespaced by the integration’s name slug

There’s no difference between a system integration tool and a custom integration tool from the agent’s perspective. Both go through the same MCP gateway.

Custom vs System Integrations

	System Integrations	Custom Integrations
Source	Global registry (managed by RubixKube)	Tenant self-served
Protocol	Determined by registry	`mcp` or `rest` (your choice)
Visibility	All tenants (based on config)	Your tenant only
Tool definitions	From registry	You provide them
Deletion	Disable only	Hard delete
Plan	All plans	Enterprise only

What You Learned

Available system integrations (Slack, PagerDuty, Prometheus, Webhooks)
Notification rules and delivery channels
How to register private MCP servers and REST APIs as custom integrations
Authentication options: Bearer, OAuth 2.1, API Key, Basic Auth
How custom integrations appear automatically in the MCP gateway

Using Agent Skills — Extend agents with structured workflows
Using Agents & Tools — Monitor agent health and capabilities
Dashboard — Your command center for infrastructure health

Need Help?

Contact Support

Email: connect@rubixkube.ai
Please include your Tenant ID (Settings → Organization), timestamp, and screenshots.

Troubleshooting Guide

Step-by-step fixes for common issues across Dashboard, Insights, Agents, and more.

FAQ

Answers to common questions about setup, RCA, agents, and docs.

Docs Navigation

Browse all guides to learn workflows and best practices.

​Managing Integrations

​System Integrations

Slack

​Get incident notifications in Slack

PagerDuty

​Page on-call for critical incidents

Prometheus

​Enhanced metrics collection

Webhooks

​Custom integrations

​Notification Rules

​Custom Integrations

​Two Protocols

MCP Server

REST API

​Adding an MCP Server

​Adding a REST API

​Managing Custom Integrations

​Editing a Custom Integration

​Other Integration Actions

​Authentication

​OAuth Flows

​How Custom Integrations Appear to Agents

​Custom vs System Integrations

​What You Learned

​Related Guides

​Need Help?

Contact Support

Troubleshooting Guide

FAQ

Docs Navigation

Managing Integrations

System Integrations

Get incident notifications in Slack

Page on-call for critical incidents

Enhanced metrics collection

Custom integrations

Notification Rules

Custom Integrations

Two Protocols

Adding an MCP Server

Adding a REST API

Managing Custom Integrations

Editing a Custom Integration

Other Integration Actions

Authentication

OAuth Flows

How Custom Integrations Appear to Agents

Custom vs System Integrations

What You Learned

Related Guides

Need Help?