Overview
Connect Sazabi to external services like Slack, Linear, and Datadog through MCP connectors.
MCP connectors let Sazabi use tools from external services. When you connect an MCP provider, Chat gains the ability to interact with that service, such as creating Linear issues, sending Slack messages, or querying Datadog metrics.
What are MCP connectors?
MCP connectors are connections between Sazabi and external MCP servers. Each connector gives Sazabi access to a set of tools that the external service provides.
For example, when you connect the Linear MCP connector:
- Sazabi discovers Linear's available tools (create issue, list projects, etc.)
- Chat can use these tools when helping you
- You can ask Sazabi to "create a Linear issue for this bug" and it will
How connectors work
OAuth authentication
Most connectors use OAuth to authenticate. You authorize Sazabi to access the external service on your behalf, and Sazabi securely stores the credentials.
Tool discovery
Once connected, Sazabi queries the MCP server to discover available tools. These tools are then available to Chat.
Dynamic loading
Tools are loaded dynamically when Chat needs them. You do not need to configure which tools to use; Sazabi selects the appropriate tools based on your requests.
Available connectors
Sazabi provides pre-configured connectors for popular services:
Attio
Search CRM records, manage lists and tasks, and pull meeting and email context from Attio.
Slack
Send messages to channels and users, manage conversations, and integrate with Slack workflows.
Linear
Create and manage issues, projects, and cycles in Linear.
Datadog
Query metrics, create monitors, and access Datadog capabilities.
incident.io
Create and manage incidents, access runbooks, and coordinate responses.
Supabase
Query databases, manage authentication, and access Supabase features.
Sentry
Access error data, manage issues, and integrate with Sentry workflows.
Custom connectors
In addition to pre-configured connectors, you can connect any MCP-compatible server:
Custom MCP Server
Connect to any MCP server with URL and authentication configuration.
Backends vs connectors
It is important to understand the difference between backends and MCP connectors:
| Type | Purpose | Data flow | Example |
|---|---|---|---|
| Backend | Query existing data | Sazabi reads from external service | "Show me Datadog logs from the last hour" |
| Connector | Access tools and actions | Sazabi calls external service APIs | "Create a Datadog monitor for CPU usage" |
Backends let Sazabi query data that exists in external platforms. Chat can search and analyze this data when answering questions.
Connectors let Sazabi use tools and take actions. Chat can create resources, send messages, and interact with external services.
Some services support both modes:
- Datadog as a backend: Query logs and metrics stored in Datadog
- Datadog as a connector: Create monitors, dashboards, and incidents
Managing connectors
Viewing connected services
Go to Settings -> MCP Connectors to see all connected MCP services. Each connection shows:
- The service name and icon
- Connection status
- Available tools
Disconnecting a service
To disconnect an MCP service:
- Go to Settings -> MCP Connectors.
- Find the service you want to disconnect.
- Click the service to open its details.
- Click Disconnect and confirm.
Disconnecting removes Sazabi's access to that service. Any workflows or automations that depend on the connector will stop working.
Security
MCP connectors use OAuth where supported, which means:
- Sazabi never sees your password for external services
- You control what permissions Sazabi has
- You can revoke access at any time from Sazabi or the external service
For custom MCP servers using header-based authentication, credentials are encrypted at rest and only decrypted when making requests to the MCP server.