Agent Connectors
Connect Codatum Agent to external APIs and MCP servers
Agent Connectors allow Codatum Agent to connect to external APIs and MCP (Model Context Protocol) servers such as GitHub, Slack, and Notion. You can add a built-in connector or register a custom MCP server or REST/GraphQL API.
Key features
Built-in connectors
Add connectors for services including GitHub, Slack, Notion, Atlassian, Salesforce, HubSpot, Linear, Airtable, PagerDuty, Sentry, Stripe, Datadog, dbt Cloud, Google Drive, and Workato.
Custom connectors
Register an MCP server or REST/GraphQL API endpoint that is not included as a built-in connector.
Credential management
Configure OAuth credentials, API keys, and other credentials at workspace or personal scope.
Tool discovery
Review the tools provided by an MCP connector.
AI Profile access control
Configure connector access as off, selected connectors only, or all connectors for each AI Profile.
Connector types
MCP
Connects to an external MCP server and allows Codatum Agent to discover and execute its tools. This type is used for services that provide an MCP server, including Notion, Atlassian, Salesforce, Sentry, Stripe, and Datadog.
Direct API
Sends requests directly to an external REST or GraphQL API using a registered API key or other credential.
The built-in GitHub connector accesses the GitHub REST API directly instead of using an MCP server. Configure a GitHub Personal Access Token or another supported credential.
Built-in connectors
GitHub API
Direct API
Access repositories, Issues, Pull Requests, users, and organizations
Slack Web API
Direct API
Access channels, messages, users, and other Slack resources
HubSpot API
Direct API
Access CRM contacts, companies, deals, and tickets
Linear API
Direct API
Access Issues, projects, teams, and cycles
Airtable API
Direct API
Access bases, tables, records, and fields
PagerDuty API
Direct API
Access incidents, services, and on-call schedules
Notion MCP
MCP
Search and edit pages and content in a Notion workspace
Atlassian MCP
MCP
Connect to Jira Issues and Confluence knowledge bases
Salesforce MCP
MCP
Access Salesforce records and queries
Sentry MCP
MCP
Access Issues, projects, events, and debugging information
Stripe MCP
MCP
Access customers, invoices, and payments
Datadog MCP
MCP
Access logs, metrics, traces, and incidents
dbt Cloud MCP
MCP
Access the Semantic Layer, Discovery, and development context
Google Drive MCP
MCP
Access files and documents in Google Drive
Workato MCP
MCP
Access recipe-based tools and workflow automation context
Configuration
Go to
Workspace Settings>Agent Connectorsand selectAdd connector.Select a built-in connector or configure a custom connector with an MCP server URL or API endpoint.
Select workspace or personal credential scope.
Configure OAuth or enter an API key or other secret under connector credentials.
Allow the connector in the AI Profile's connector access settings.
After configuration, Codatum Agent can discover and use the connector's tools or APIs when needed during a conversation.
Approval
Connector tool calls and API requests require user approval by default. Users can enable auto-approval for MCP Tool Execution and Connector HTTP Request in their Agent settings.
Review the requested operation before approving it. Depending on the connector and tool, the operation may modify data in the external service.
Limitations
The server URL of an MCP connector cannot be changed after creation. Delete and recreate the connector to use a different URL.
Connector access must be explicitly allowed in the AI Profile. The default is off.
Restrictions are applied to external destinations to prevent unintended access to internal networks and other protected addresses.
Last updated
Was this helpful?

