Appearance
Agent connectors
An agent connector is an external integration used by the AI agent. You can create and manage them from global nav > Workspace settings > Agent Connectors. Availability can also be restricted through Connector access in AI profiles.
Creating and managing
- Open global nav > Workspace settings > Agent Connectors.
- Select New connector.
- Choose a built-in connector, or select Custom.
- Enter the settings, then select Create.
Types
| Type | Description |
|---|---|
| MCP | Connects to an MCP server and uses its published tools |
| Direct API | Calls an HTTP API directly |
When creating a custom connector, you can choose MCP or Direct API under Connector type. For built-in connectors, the type is already fixed.
Settings
Some items aren't shown, depending on the type and authentication method.
| Item | Description |
|---|---|
| Name | The connector's display name |
| Built-in connector | Shown when created from a built-in connector (can't be changed) |
| Overview | A short description always passed to the agent. For Direct API, you can set this from creation; for MCP, you set it when editing after creation |
| Skill doc | Detailed instructions loaded only when needed. Shown under the same conditions as Overview |
| Server URL | The MCP connection URL. Can't be changed after creation |
| Auth scope | For MCP: Workspace (API key) / Personal (OAuth) (when the built-in connector offers both). For Direct API: Workspace / Personal |
| Endpoint prefix | The API base URL for Direct API. Can't be changed after creation |
| Secret keys | The key names and values used for Direct API, or for MCP API key authentication |
| Enabled | Turning this off disables the connector |
For MCP OAuth, you can optionally specify an OAuth client (client ID / client secret) and OAuth scopes under Advanced settings. If left blank and the MCP server supports it, Dynamic Client Registration is used, and the scopes requested are whatever the server publishes.
For MCP (OAuth), each user connects individually using personal authentication from the connector detail screen. Credentials for MCP (API key) and Direct API (workspace) are shared across the workspace. Personal-scope Direct API authentication is managed under Connector authentication in global nav > Workspace settings > Personal settings.
Built-in connectors
You can create a connector from the following built-in options. This list may be added to or changed without notice.
| Name | Type | Description |
|---|---|---|
| Datadog MCP | MCP | Connects to Datadog logs, metrics, traces, incidents, and more |
| dbt Cloud MCP | MCP | Connects to dbt Cloud's Semantic Layer, Discovery, and development context |
| GitHub API | Direct API | Retrieves repositories, issues, pull requests, and more |
| HubSpot API | Direct API | Retrieves CRM contacts, companies, deals, tickets, and more |
| Intercom MCP | MCP | Connects to conversations, contacts, companies, and Help Center content |
| Linear API | Direct API | Retrieves issues, projects, teams, and more |
| Airtable API | Direct API | Retrieves bases, tables, records, fields, and more |
| Notion MCP | MCP | Connects to workspace search, page operations, and content editing |
| Atlassian MCP | MCP | Connects to Jira issues and the Confluence knowledge base |
| Google Drive MCP | MCP | Connects to Google Drive files and Workspace documents |
| Salesforce MCP | MCP | Connects to Salesforce records and queries |
| Slack Web API | Direct API | Operates on channels, messages, users, and more |
| PagerDuty API | Direct API | Retrieves incidents, services, on-call schedules, and more |
| Sentry MCP | MCP | Connects to issues, projects, events, and more |
| Stripe MCP | MCP | Connects to customers, invoices, payments, and document operations |
| Workato MCP | MCP | Connects to recipe-derived tools and business automation context |
| Composio Connect | MCP | Connects to many apps through Composio Connect |