​

Managing Integrations

​

System Integrations

​

Notification Rules

• All incidents
• RCA report completion
• Cluster disconnection

• PagerDuty alerts
• Webhook calls
• Email (coming soon)

​

Custom Integrations

​

Two Protocols

​

Adding an MCP Server

1

Open Integrations

Navigate to Integrations in the left sidebar.

2

Click + Add Custom Integration

Select MCP Server as the protocol type.

3

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)

4

Configure MCP Connection

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.

5

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.

​

Adding a REST API

1

Select REST API Protocol

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

2

Enter Metadata

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

3

Enter Base URL and Auth

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)

4

Define Tools

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

5

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

​

Other Integration Actions

• 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.

​

Authentication

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

{
  "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
  }
}

{
  "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
  }
}

{
  "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"
  }
}

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

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

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

​

OAuth Flows

​

How Custom Integrations Appear to Agents

• 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

​

Custom vs System Integrations

​

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

​

Related Guides

• 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?