Appearance
Agent connectors Beta
Agent connectors make tools and APIs from external services available to the AI agent and MCP clients.
You can create and manage them from global nav > Workspace settings > Agent connectors.
Availability can also be restricted through Connector access in AI profiles.
INFO
This feature is in beta. The specification might change without notice.
Using connectors from MCP clients
Codatum can act as a gateway that lets MCP clients use external services registered as agent connectors. You don't need to configure the external service credentials in the MCP client.
Available operations depend on the connected user's permissions, the connector:execute scope approved for the Codatum MCP connection, and Connector access in the selected MCP access profile. Connector access from an AI Profile doesn't apply to direct MCP calls. See MCP client settings for connection and scope details.
Creating and managing
You need permission to change workspace settings to create, edit, or delete connectors.
- Open global nav > Workspace settings > Agent connectors.
- Select Personal auth connectors or Shared auth connectors.
- Under Personal auth connectors, each user uses their own external service account and permissions.
- Under Shared auth connectors, the workspace shares the same credentials, such as a service account or API key.
- In both catalogs, Connector access in AI profiles controls which connectors are available in Codatum.
- Choose a built-in connector from the selected catalog.
- Enter a service name in
Search by service name...to find connectors. - You can filter by the following conditions:
- Category (Collaboration / Sales & Marketing / Engineering / Data & Analytics / Operations)
- Market (Global / Japan)
- Connector type (MCP / API)
- Status (Live-tested / Not live-tested / Upon request)
- Filters start unselected and show every connector in the selected catalog.
- If you don't enter a search term or select a category, the catalog shows Popular connectors and then connectors grouped by category.
- When you start a search, the catalog shows only matching connectors grouped by category.
- The same service can appear in both catalogs.
- The bottom of each card shows the type (MCP / API).
- Connectors that Codatum has tested show Live-tested with a check icon.
- Enter a service name in
- Review its description, authentication method, and official website in the catalog detail.
- Administrators and developers can expand Connection details to view technical information for the selected catalog.
- Its values are paired with explicit labels such as Authentication method, OAuth client registration, OAuth App, and Credentials.
- Access in Codatum links to the AI profile settings.
- If the connector is available for self-service setup, select Install connector.
- A connector marked Verification pending can't be added until live testing is complete.
- To request access, select Contact us on its detail page.
- If it's marked Upon request, also select Contact us on the detail page.
- Confirm the connector and request type, enter optional details, then select Submit request.
- For a destination not in the catalog, select Create custom connector to configure an MCP URL or API manually.
- If Required setup before connecting appears on the connection settings page, complete those instructions. Enter the connector settings, then select Create.
- For a personal OAuth MCP connector, you can then select Connect and set up or Set up later.
- Connect and set up authenticates your account and completes connector readiness.
- Set up later opens the connector details without authenticating.
- Use Installed to view, edit, or delete created connectors.
- Catalog cards and details show Installed when the same connector already exists in that authentication catalog.
- Installed connectors on the detail page lists the existing connectors.
- Select a connector in the list to review its settings.
- To add another instance of the same connector, select Install another below the list.
Connectors managed in Slack integration
Connecting a Slack workspace in Workspace settings > Slack integration automatically adds a shared Slack connector. You don't need to enter a token or authenticate each user separately.
To use it from the AI agent, allow the connector individually or select All connectors under Connector access in an AI Profile. Slack integration settings show the number of AI Profiles that can use the connection. Select the count to view the connector details and the list of AI Profiles.
If permissions are missing, Slack integration settings show a notice and Update permissions. Re-authenticate to grant the additional permissions. Operations covered by existing permissions remain available before the update.
Allow Codatum Agent to start from Slack controls whether you can start Codatum Agent from Slack. AI Profiles with connector access can use the Slack connector even when this setting is off.
When you send a message to the AI agent from Slack, the agent adds an 👀 reaction to acknowledge it. A single progress card in the thread collects results such as completed data searches and SQL executions. Its heading shows the latest activity. The answer appears when the agent finishes. If approval is required, the progress display ends and a separate message asks for your confirmation.
With a built-in Slack connector (managed in Slack integration, or registered with a bot token), the AI agent can use tools that complete a Slack operation in a single run: posting a message, sharing a file, and searching channels. Specify the channel as #name or a channel ID. The bot joins public channels automatically. To send to a private channel, invite the bot to the channel first.
Running these tools requires approval like other connector tools. To skip approval, use Connector Tool Execution in the AI agent user settings.
The connector is labeled Managed in Slack integration. You can't change its name, credentials, or enabled state, or delete it from connector settings. Select Edit instructions to override the overview and skill doc. Select Open Slack integration to manage the connection.
If updating the connector fails after connecting or re-authenticating, you return to Slack integration settings with an error. Re-authenticate to try again. A failed connector update during disconnection also displays an error. The Slack connection change is already saved. The connector update is not retried automatically.
Disconnecting Slack leaves the connector disabled. Reconnecting after disconnection adds a new connector, which you must allow again in AI Profiles that use an individual allow list. Re-authenticating an existing connection or changing the permission to start Codatum Agent from Slack preserves connector permissions and instruction overrides.
The AI agent can export a Canvas as PDF or HTML and send it to a Slack channel. Files are limited to 50 MB. See Limits and constraints. Exported temporary files are available in the same conversation for 24 hours.
The AI agent can run refreshable and interactive reports, export published pages as PNG or PDF, and send the files. Running and exporting require publish permission on the source notebook and the connections included in the output. The saved results in the report remain unchanged. Interactive reports also accept parameter values for the run.
Sending uses the connector access permissions and the Auto-approve Tool Execution settings: Connector Tool Execution when sending with the file sharing tool, and Connector HTTP Request when calling the HTTP API directly.
Types
| Type | Description |
|---|---|
| MCP | Connects to an MCP server and uses its published tools |
| API | Calls an HTTP API directly |
When creating a custom connector, you can choose MCP or 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 |
|---|---|
| Connector type | Select MCP or API when you create a custom connector. |
| Name | The connector's display name |
| Enabled | Turning this off disables the connector. |
| Authentication scope | For a custom API that uses API key / token authentication, select Workspace or Personal. Manually configured APIs that use OAuth use personal authentication. |
| Server URL | The connection URL for a custom MCP connector. You can't change it after creation. It isn't shown for built-in connectors. |
| Authentication method | For MCP, select a method supported by the connector: Personal (OAuth), Personal (API key / token), or Workspace (API key / token). |
| OAuth client (required) / OAuth client (optional) | The client ID and client secret used for OAuth authentication. Whether they're required depends on the connector. |
| OAuth scopes (required) / OAuth scopes (optional) | The scopes requested for OAuth authentication. For a built-in API, the connector definition fixes these scopes. |
| Request headers | The HTTP header templates used for MCP API key / token authentication. They come from the built-in connector and can't be changed |
| Endpoint prefix | The base URL for a custom API. You can't change it after creation. It isn't shown for built-in connectors. |
| Additional allowed URL prefixes (optional) | In Additional settings for a custom API, enter up to 10 HTTPS URL prefixes, one per line. You can edit them after creation. Requests to these destinations do not include connector credentials. |
| Secret keys | The key names and values used for API or MCP API key / token authentication. For a built-in connector, follow the hint shown for each key. Values are expanded into the request header templates |
| Overview (optional) / Overview override (optional) | Available under Additional settings. This short description is always passed to the agent. For a built-in connector, it overrides the default overview. |
| Skill doc (optional) / Skill doc override (optional) | Available under Additional settings. These detailed instructions are loaded only when needed. For a built-in connector, they override the default skill doc. |
Some built-in API connectors show additional settings that identify the connection target, such as Organization slug for Sentry. Follow the hint shown for each item. You can change these values after creation. The agent can't use the connector until they are set.
For OAuth authentication, the OAuth client and OAuth scopes appear with the other primary settings.
- For MCP, if the OAuth client is blank and the MCP server supports it, Dynamic Client Registration is used.
- For MCP, if OAuth scopes are blank, the scopes advertised by the server are requested.
- If a built-in MCP connector predefines OAuth scopes, the scopes field can't be left empty.
- Manually configured API OAuth requires the client ID, client secret, and OAuth scopes shown by the built-in connector.
For built-in connectors that can't use Dynamic Client Registration, a workspace administrator creates an OAuth app with the provider and enters its client ID when a Codatum shared app isn't available. This applies to the following providers:
- Microsoft
- GitHub
- HubSpot
- Salesforce
- Box
- Asana
- Slack
- PagerDuty
- Gong
- Front
- Gainsight CS
- Dropbox
The following providers also require a client secret:
- GitHub
- HubSpot
- Box
- Asana
- Slack
- PagerDuty
- Gong
- Front
- Gainsight CS
For MCP, when a Codatum shared app is available, leave the OAuth client fields blank, or enter your own app credentials to override it. Manually configured API OAuth requires the credentials of the app shown by the built-in connector.
Google Workspace MCP uses a Developer Preview feature with your own OAuth app. Before using it, confirm its current availability and requirements with Google.
Google's user data policy (Limited Use) doesn't allow Google Workspace data to be used to train or improve generalized AI or machine learning models. Codatum-managed AI models meet this requirement. For AI profiles that use your own API key, use an AI service plan and settings that don't use input data for training.
For live-tested connectors that support your own app, the creation form shows the following:
- The app creation page
- App type
- Required values
- Official setup guide
For MCP, set the app's redirect URI (callback URL) to https://app.codatum.com/oauth/mcp/callback. For API, use https://app.codatum.com/oauth/direct-api/callback.
How credentials are handled depends on the catalog you select.
- Under Personal auth connectors, each user connects with their own OAuth account or API key / token.
- Changing the OAuth client or OAuth scopes disconnects existing personal authentication and requires each user to reconnect.
- Under Shared auth connectors, the workspace shares credentials registered by a workspace administrator.
- Personal-scope authentication is managed under Connector authentication in account settings.
Readiness and connection status
In the connector list, Readiness shows the state of the connector as a whole. Your connection shows the current user's state. Neither state must be completed before the other.
For a connector under Personal auth connectors, readiness is complete when a workspace administrator connects their credentials and loads the tools. For a connector under Shared auth connectors, readiness is complete when a workspace administrator registers the shared credentials and loads the tools.
Readiness
For API connectors, workspace readiness is Available when the connector is enabled and, for organization scope, shared credentials are registered.
| Display | Description |
|---|---|
| Disabled | The connector is disabled. |
| Not ready | The connector isn't ready for use. |
| Available | The connector is ready for use. |
| Action required | Connection or readiness failed. The detail page shows an error category and the time of the check. |
Your connection
| Display | Description |
|---|---|
| Not connected | Select Authenticate under Your connection for OAuth, or register an API key / token under Connector authentication in account settings. |
| Connected | The current user has completed personal authentication. |
| Not required | The connector uses shared workspace credentials instead of personal authentication. |
Member connections
Workspace owners can see who has connected personal credentials.
The list Member count column shows how many people have connected personal credentials. Shared auth connectors show —. Installed connectors on a catalog detail page shows the same count.
Member connections on the connector detail page shows the following:
| Item | Description |
|---|---|
| Member | The user who connected personal credentials |
| Connected | When the personal credentials were connected |
| Last used | When this connector was last used with that user's credentials. Unused connections show Not used. |
Shared auth connectors don't show who used them. Workspace owners can see Last used for the shared workspace credentials on the detail page. Unused credentials show Not used. Connectors managed in Slack integration don't show last used.
When action is required
- Review the error under Readiness on the connector detail page.
- Correct the OAuth app or MCP server settings.
- If personal OAuth authentication isn't complete, select Authenticate in the Your connection section. For a personal API key / token, open Connector authentication in account settings and register it.
- If you're authenticated and can change workspace settings, select Retry setup. Otherwise, ask a workspace administrator to complete readiness.
When Datadog authentication fails
The Datadog connector requires the Datadog site selected at creation to match the site of the target Datadog organization.
- If the authorization screen shows "Mismatching redirect URI", a Datadog admin of the target organization must enable MCP Access under Organization Settings > Preferences and add
https://app.codatum.com/oauth/mcp/callbackto MCP OAuth Redirect URLs - If authentication fails at the end, when returning to Codatum, the connector's Datadog site doesn't match the organization's site. Check the Site shown on the Datadog sign-in and organization switcher screens. Custom subdomain URLs such as
example.datadoghq.comdon't indicate the site - You can't change the Datadog site after creation. If it doesn't match, delete the connector and re-create it with the correct site
Built-in connectors
The following built-in connectors appear in the catalog. This list may be added to or changed without notice.
Connectors marked Upon request aren't currently available for self-service setup.
The detail page shows the verification status as Live-tested or Not live-tested.
- Codatum has tested connectors marked Live-tested with a live service account.
- Connectors marked Not live-tested are based on official specifications but can't be added until Codatum completes live testing. You can request access from the connector detail page.
Collaboration
| Name | Type | Connection | Description |
|---|---|---|---|
| Linear | API | Organization client credentials · Live-tested | Retrieves issues, projects, teams, and more. |
| Airtable | API | Organization service account · Not live-tested | Retrieves bases, tables, records, fields, and more that the service account can access. |
| Notion | MCP | Personal OAuth · Live-tested | Connects to workspace search, page operations, and content editing available to the authenticated user. |
| Notion | API | Organization internal connection token · Live-tested | Retrieves pages, data sources, and users shared with an internal connection. |
| Atlassian | MCP | Personal OAuth · Live-tested | Connects to Jira issues and the Confluence knowledge base. |
| Google Drive | MCP | Personal OAuth · Own app · Google Developer Preview · Live-tested | Connects to Google Drive files and Workspace documents. |
| Gmail | MCP | Personal OAuth · Own app · Google Developer Preview · Live-tested | Connects to Gmail messages, threads, and drafts. |
| Google Calendar | MCP | Personal OAuth · Own app · Google Developer Preview · Live-tested | Connects to Google Calendar calendars and events with read-only access. |
| Google Docs | MCP | Personal OAuth · Own app · Google Developer Preview · Live-tested | Connects to reading and updating Google Docs. |
| Google Sheets | MCP | Personal OAuth · Own app · Google Developer Preview · Live-tested | Connects to reading and updating Google Sheets. |
| Google Slides | MCP | Personal OAuth · Own app · Google Developer Preview · Live-tested | Connects to reading and updating Google Slides. |
| Google Chat | MCP | Personal OAuth · Own app · Google Developer Preview · Live-tested | Connects to Google Chat spaces and messages. |
| Google Docs | API | Organization service account · Live-tested | Retrieves Google Docs shared with the service account. |
| Google Docs | API | Personal OAuth · Own app · Live-tested | Retrieves Google Docs available to the authenticated user with read-only access. |
| Google Drive | API | Organization service account · Live-tested | Retrieves files and folders shared with the service account. |
| Google Drive | API | Personal OAuth · Own app · Live-tested | Retrieves files and folders available to the authenticated user with read-only access. |
| Google Sheets | API | Organization service account · Live-tested | Retrieves Google Sheets shared with the service account. |
| Google Sheets | API | Personal OAuth · Own app · Live-tested | Retrieves Google Sheets available to the authenticated user with read-only access. |
| Google Slides | API | Organization service account · Live-tested | Retrieves Google Slides presentations shared with the service account. |
| Google Slides | API | Personal OAuth · Own app · Live-tested | Retrieves Google Slides available to the authenticated user with read-only access. |
| Google Calendar | API | Personal OAuth · Own app · Live-tested | Retrieves calendars and events available to the authenticated user with read-only access. |
| Gmail | API | Personal OAuth · Own app · Live-tested | Retrieves the authenticated user's messages, threads, labels, and drafts with read-only access. |
| Google Chat | API | Personal OAuth · Own app · Live-tested | Retrieves spaces and messages available to the authenticated user with read-only access. |
| Microsoft Outlook Calendar | MCP | Personal OAuth · Own app · Live-tested | Connects to Outlook calendar. |
| Microsoft Outlook Mail | MCP | Personal OAuth · Own app · Live-tested | Connects to Outlook mail. |
| Microsoft OneDrive | MCP | Personal OAuth · Own app · Live-tested | Connects to OneDrive files. |
| Microsoft SharePoint | MCP | Personal OAuth · Own app · Live-tested | Connects to SharePoint sites, lists, and files. |
| Microsoft Teams | MCP | Personal OAuth · Own app · Live-tested | Connects to Teams chats and channels. |
| Microsoft User Directory | MCP | Personal OAuth · Own app · Live-tested | Connects to Microsoft 365 user profiles and org structure. |
| Microsoft Word | MCP | Personal OAuth · Own app · Live-tested | Connects to Word documents. |
| Slack | API | Organization bot token · Live-tested | Operates on channels, messages, users, and more. |
| Workato | MCP | Personal OAuth · Live-tested | Connects to recipe-derived tools and business automation context. |
| Composio Connect | MCP | Organization consumer API key / Personal OAuth · Live-tested | Connects to many apps through Composio Connect. |
| Linear | MCP | Personal OAuth · Live-tested | Connects to Linear issues and projects. |
| Airtable | MCP | Personal OAuth · Live-tested | Connects to Airtable bases and records. |
| Asana | MCP | Personal OAuth · Own app · Live-tested | Connects to Asana tasks and projects. |
| Asana | API | Organization service account · Not live-tested | Retrieves workspaces, projects, and tasks. |
| Box | MCP | Personal OAuth · Own app · Live-tested | Connects to Box files. |
| Canva | MCP | Personal OAuth · Upon request | Connects to Canva designs. |
| Egnyte | MCP | Personal OAuth · Live-tested | Connects to Egnyte files. |
| Fireflies | MCP | Personal OAuth · Live-tested | Connects to Fireflies transcripts. |
| Miro | MCP | Personal OAuth · Live-tested | Connects to Miro boards. |
| monday.com | MCP | Personal OAuth · Live-tested | Connects to monday.com boards. |
| Granola | MCP | Personal OAuth · Live-tested | Connects to Granola meeting notes. |
| Slack | MCP | Personal OAuth · Own app · Live-tested | Connects to messages, channels, files, users, canvases, and lists. |
| ClickUp | MCP | Personal OAuth · Live-tested | Connects to tasks, lists, folders, documents, and chat. |
| Dropbox | MCP | Personal OAuth · Own app · Live-tested | Connects to files, folders, search, sharing, and file requests. |
| Shortcut | MCP | Personal OAuth · Live-tested | Connects to stories, epics, and iterations. |
| kintone | API | Organization API token · Live-tested | Connects to records and operational data in configured apps. |
| Chatwork | API | Personal API token · Live-tested | Connects to rooms, messages, members, and tasks. |
| Backlog | API | Personal API token · Upon request | Connects to projects, issues, wikis, and users. |
| ANDPAD | API | Organization OAuth client · Upon request | Connects to construction and project data. |
| microCMS | API | Organization API key · Upon request | Connects to content and schemas. |
| TimeRex | API | Personal OAuth client · Upon request | Connects to scheduling data. |
Sales & Marketing
| Name | Type | Connection | Description |
|---|---|---|---|
| HubSpot | API | Organization Account Service Key · Live-tested | Retrieves CRM contacts, companies, deals, tickets, and more. |
| KARTE | API | Organization access token · Live-tested | Reviews and edits KARTE campaigns, actions, and segments through KARTE API v2. |
| Shopify | API | Organization client credentials · Live-tested | Connects to products, orders, customers, inventory, and more through Shopify Admin API. |
| Intercom | MCP | Personal OAuth · Live-tested | Connects to conversations, contacts, companies, and Help Center content. |
| Salesforce | MCP | Personal OAuth · Own app · Live-tested | Connects to Salesforce records and queries. |
| Salesforce | API | Organization client credentials · Live-tested | Connects to Salesforce REST API through an external client app and a dedicated integration user. |
| HubSpot | MCP | Personal OAuth · Own app · Live-tested | Connects to HubSpot CRM. |
| Attio | MCP | Personal OAuth · Live-tested | Connects to Attio CRM. |
| Attio | API | Organization workspace access token · Live-tested | Retrieves objects, records, lists, and members. |
| Close | MCP | Personal OAuth · Live-tested | Connects to Close CRM. |
| Semrush | MCP | Personal API key · Live-tested | Connects to SEO, traffic, backlink, competitor, and project data. |
| Ahrefs | MCP | Personal OAuth / API key · Live-tested | Connects to SEO, keyword, backlink, and competitor research data. |
| Apollo | MCP | Personal OAuth · Live-tested | Connects to sales intelligence, prospects, and enrichment. |
| Apollo | API | Organization API key · Live-tested | Retrieves people, accounts, deals, and saved lists. |
| Gong | MCP | Personal OAuth · Own app · Not live-tested | Connects to account, deal, contact, and revenue intelligence. |
| Klaviyo | MCP | Personal OAuth · Live-tested | Connects to profiles, campaigns, flows, segments, and delivery metrics. |
| Klaviyo | API | Organization private API key · Not live-tested | Retrieves profiles, lists, segments, campaigns, and metrics. |
| Braze | MCP | Personal OAuth · Upon request | Connects to campaigns, Canvases, segments, analytics, and catalogs. |
| Customer.io | MCP | Personal OAuth · Live-tested | Connects to profiles, campaigns, journeys, and delivery metrics. |
| Front | MCP | Personal OAuth · Own app · Not live-tested | Connects to conversations, inboxes, contacts, messages, and drafts. |
| Gainsight CS | MCP | Personal OAuth · Own app · Not live-tested | Connects to companies, CTAs, Success Plans, Timeline, and scorecards. |
| Webflow | MCP | Personal OAuth · Live-tested | Connects to sites, pages, and CMS content. |
| Wix | MCP | Personal OAuth · Not live-tested | Connects to sites, CRM, stores, and bookings. |
| Sanity | MCP | Personal OAuth · Live-tested | Connects to content, datasets, and projects. |
| Sansan | API | Organization API key · Upon request | Connects to people, business card, tag, and organization data after Open API access is coordinated. |
| BASE | API | Organization OAuth client · Upon request | Connects to shops, products, and orders after Direct API connectors support OAuth. |
| MiiTel | MCP | Personal provider-managed authentication · Upon request | Connects to call and meeting analytics after provider coordination. |
| スマレジ | API | Organization OAuth client · Upon request | Connects to sales, product, customer, and inventory data. |
| Re:lation | API | Organization API key · Upon request | Connects to inquiries, customers, and messages. |
| STORES | API | Organization OAuth client · Upon request | Connects to commerce data. |
| SalesNow | API | Organization API key · Upon request | Connects to company data. |
| Mazrica Sales | API | Organization API key · Upon request | Connects to accounts, deals, and activities. |
| Upflow | MCP | Personal OAuth · Upon request | Connects to sales conversations and customer insights. |
| amptalk analysis | API | Organization API key · Upon request | Connects to call transcripts, summaries, and analytics. |
Engineering
| Name | Type | Connection | Description |
|---|---|---|---|
| Datadog | MCP | Personal OAuth / Organization personal access token · Live-tested | Connects to Datadog logs, metrics, traces, incidents, and more. |
| GitHub | API | Organization personal access token · Live-tested | Retrieves repositories, issues, pull requests, and more. |
| PagerDuty | API | Organization API key · Live-tested | Retrieves incidents, services, on-call schedules, and more. |
| Sentry | MCP | Personal OAuth · Live-tested | Connects to issues, projects, events, and more. |
| Sentry | API | Organization internal integration token · Live-tested | Retrieves projects, issues, and events with an internal integration token and organization slug. |
| GitHub | MCP | Personal OAuth · Own app · Live-tested | Connects to GitHub repositories, issues, and pull requests. |
| Vercel | MCP | Personal OAuth · Upon request | Connects to Vercel projects and deployments. |
| Buildkite | MCP | Personal OAuth · Live-tested | Connects to Buildkite pipelines and builds. |
| Netlify | MCP | Personal OAuth · Live-tested | Connects to Netlify sites and deployments. |
| Pulumi | MCP | Personal OAuth · Live-tested | Connects to Pulumi stacks. |
| Pulumi | API | Organization access token · Not live-tested | Retrieves stacks, update history, and resources. |
| GitLab | MCP | Personal OAuth · Live-tested | Connects to projects, issues, merge requests, pipelines, and repositories. |
| Cloudflare | MCP | Personal OAuth / Organization account API token · Live-tested | Connects to the Cloudflare API. |
| Grafana Cloud | MCP | Personal OAuth · Live-tested | Connects to metrics, logs, dashboards, alerts, and incidents. |
| PagerDuty | MCP | Personal OAuth · Own app · Not live-tested | Connects to incidents, services, schedules, and on-call rotations. |
| HENNGE One | API | Organization client credentials · Upon request | Connects to identity and access data. |
Data & Analytics
| Name | Type | Connection | Description |
|---|---|---|---|
| dbt Cloud | MCP | Personal OAuth · Live-tested / Organization service token · Live-tested | Connects to dbt Cloud's Semantic Layer, Discovery, and development context. |
| Supabase | MCP | Personal OAuth · Live-tested | Connects to Supabase projects and schema. |
| Neon | MCP | Personal OAuth · Live-tested | Connects to Neon projects and branches. |
| ThoughtSpot | MCP | Personal OAuth · Live-tested | Connects to ThoughtSpot analytics. |
| Morningstar | MCP | Personal OAuth · Not live-tested | Connects to Morningstar financial data. |
| PostHog | MCP | Personal OAuth · Live-tested | Connects to product analytics, feature flags, experiments, and session recordings. |
| Amplitude | MCP | Personal OAuth · Live-tested | Connects to analytics, taxonomy, experiments, cohorts, charts, and dashboards. |
| Mixpanel | MCP | Personal OAuth · Live-tested | Connects to events, funnels, flows, retention, and product analytics. |
| Google Analytics | API | Personal OAuth · Own app · Live-tested / Organization service account · Live-tested | Connects to Google Analytics 4 reports, realtime data, and reporting metadata. |
| Wicle | MCP | Personal OAuth · Live-tested | Connects to project settings and product analytics. |
| Hugging Face | MCP | Personal OAuth · Live-tested | Connects to models, datasets, Spaces, and papers on the Hugging Face Hub. |
| TROCCO | API | Personal API key · Upon request | Connects to users, transfer jobs, data marts, and workflows. |
Operations
| Name | Type | Connection | Description |
|---|---|---|---|
| freee | MCP | Personal OAuth · Live-tested | Connects to accounting, HR, invoicing, time tracking, and sales operations. |
| マネーフォワード クラウド会計 | MCP | Personal OAuth · Live-tested | Connects to accounting data and operations. |
| Stripe | MCP | Personal OAuth / Organization restricted API key · Live-tested | Connects to customers, invoices, payments, and document operations. |
| PayPal | MCP | Personal OAuth · Live-tested | Connects to PayPal payments. |
| Ramp | MCP | Personal OAuth · Upon request | Connects to Ramp expenses and cards. |
| Paddle | MCP | Personal OAuth · Live-tested | Connects to billing, subscriptions, and transactions. |
| SmartHR | API | Organization access token · Live-tested | Connects to employee and HR data. |
| kickflow | API | Personal API token · Live-tested | Connects to tickets, users, organization charts, and master data. |
| ジョブカン | API | Organization API key · Upon request | Connects to attendance and back-office data. |
| バクラク | API | Organization API key · Upon request | Connects to requests, approvals, and expense data after Codatum validates the API integration. |
| kaonavi | API | Organization client credentials · Live-tested | Connects to members, sheets, departments, users, and other talent management data. |
| LegalOn | API | Organization API key · Upon request | Connects to contract data. |
| KING OF TIME | API | Organization API key · Upon request | Connects to attendance, leave, and employee data. |
| Contract One | MCP | Personal provider-managed authentication · Upon request | Connects to contract data. |