> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-administrators/connectors-marketplace.md).

# Connectors-Marketplace

A connector gives an assistant or Toolbox element access to actions in a connected service. The Marketplace prefills known connection settings. An integration administrator prepares application credentials or keys where needed; with per-user OAuth, each user authorizes their own account.

These guides are for administrators. Available connectors and actions depend on your configuration, permissions and the connected service’s requirements.

{% hint style="info" %}
Application registrations, OAuth and MCP configuration are advanced topics. Ask your integration administrator to perform those steps. Enter keys only in their designated fields.
{% endhint %}

## Jump to a connector <a href="#connector-index" id="connector-index"></a>

* [Adobe Target](#adobe-target)
* [Adobe Workfront](#adobe-workfront)
* [Ahrefs](#ahrefs)
* [Airtable](#airtable)
* [Amplitude](#amplitude)
* [Artific Docs](#artific-docs)
* [Artific Outlook Mail & Calendar](#artific-outlook)
* [Asana](#asana)
* [Attio](#attio)
* [Box](#box)
* [Brevo](#brevo)
* [Cal.com](#cal-com)
* [Calendly](#calendly)
* [Canva](#canva)
* [ClickUp](#clickup)
* [Cloudflare](#cloudflare)
* [Datadog](#datadog)
* [Exa](#exa-search)
* [Figma](#figma)
* [Fireflies](#fireflies)
* [GitHub](#github)
* [GitLab](#gitlab)
* [HiBob](#hibob)
* [Higgsfield](#higgsfield)
* [HoorayHR](#hoorayhr)
* [HubSpot](#hubspot)
* [Intercom](#intercom)
* [Jira & Confluence](#atlassian)
* [Jortt](#jortt)
* [Klaviyo](#klaviyo)
* [Linear](#linear)
* [Microsoft 365 Work IQ](#microsoft-workiq)
* [Miro](#miro)
* [monday.com](#monday)
* [Moneybird (read-only)](#moneybird-readonly)
* [Notion](#notion)
* [Odoo](#odoo)
* [Pennylane](#pennylane)
* [Personio](#personio)
* [Pipedrive (beta)](#pipedrive)
* [Plaud](#plaud)
* [Pocket](#pocket)
* [PostHog](#posthog)
* [Remote](#remote)
* [Sentry](#sentry)
* [Simplicate](#simplicate)
* [Slack](#slack)
* [Smartsheet](#smartsheet)
* [Stripe](#stripe)
* [Supabase](#supabase)
* [Tally](#tally)
* [Teamleader Orbit](#teamleader-orbit)
* [Todoist](#todoist)
* [Typeform](#typeform)
* [Wrike](#wrike)
* [Zoom Meetings](#zoom-meetings)

## General steps <a href="#general-steps" id="general-steps"></a>

These steps apply to all entries below. Follow the additional service-specific setup for the connection you choose.

1. Open **Organization management → Shared connectors → Add connector → Marketplace** and select the service.
2. Follow its requirements and settings below. Keep automatic discovery enabled when indicated. For manual OAuth, enter the registered application credentials; for a token, enter only the key without a Bearer prefix.
3. Save OAuth entries with **Save & connect**. For **None** or **Bearer token**, select **Test connection** and then **Add connector**.
4. Open the assistant’s **Connectors → Add connector → Use existing** and select the shared connector.
5. For **OAuth — Per-user**, each user selects **Connect** and authorizes their own account. A shared token uses that token’s rights for everyone; **None** needs no sign-in.
6. Select **Refresh connector** from the assistant and review **Manage actions**. The organization administrator controls shared actions under **Shared connectors**. Review new actions after refresh.

A shared per-user connector has no personal token to test at organization scope. Complete sign-in and refresh from the assistant. Allow pop-ups for the Artific domain if the sign-in window does not open.

After changing OAuth rights, update the service and connector, connect again and refresh. When replacing a key, update the connector and revoke the old key after the replacement works. Removing a connector from an assistant does not automatically revoke external app consent; revoke it at the service to end all granted access.

General guidance: [Shared connectors](https://docs.artific.nl/en/for-administrators/organization/shared-connectors.md) and [Connector authentication](https://docs.artific.nl/en/for-administrators/assistants/connectors.md).

## Adobe Target <a href="#adobe-target" id="adobe-target"></a>

### Preparation <a href="#adobe-target-preparation" id="adobe-target-preparation"></a>

Use an active Adobe Target license within Adobe Experience Cloud and the correct organization. Ask the Adobe administrator to check the Target role: Observer for reading, Editor for creating, or Approver for activation and deactivation as well. No separately supplied application credentials are required for this OAuth entry.

### Settings <a href="#adobe-target-settings" id="adobe-target-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://targetmcp.adobe.io/mcp`  |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#adobe-target-access-and-usage" id="adobe-target-access-and-usage"></a>

Select the correct Adobe profile and Experience Cloud organization during authorization. This is specifically a Target integration; a Creative Cloud account alone does not provide Target access.

### Check <a href="#adobe-target-check" id="adobe-target-check"></a>

“List the names and statuses of up to three Target activities. Do not edit or activate anything.”

### Troubleshooting <a href="#adobe-target-troubleshooting" id="adobe-target-troubleshooting"></a>

| Problem                                | What to check                                                    |
| -------------------------------------- | ---------------------------------------------------------------- |
| Data belongs to the wrong organization | Reconnect and select the correct Adobe profile and organization. |
| Writing actions are unavailable        | Check Target roles and allowed actions.                          |

### Further information <a href="#adobe-target-further-information" id="adobe-target-further-information"></a>

* [Official documentation](https://experienceleague.adobe.com/en/docs/target/using/integrate/mcp/target-mcp-get-started)

[Back to the connector index](#connector-index)

## Adobe Workfront <a href="#adobe-workfront" id="adobe-workfront"></a>

### Preparation <a href="#adobe-workfront-preparation" id="adobe-workfront-preparation"></a>

Use an active Workfront account in an Adobe IMS-enabled instance. Have the administrator check System Preferences → Read-only MCP tools and Write MCP tools; writing is off by default. If a custom callback is rejected, check its exact value under MCP preferences → Authorized redirect URLs. Use <https://app.artific.nl/oauth/callback> or that path on your Artific domain, not a wildcard. Workfront Planning also needs the corresponding package.

### Settings <a href="#adobe-workfront-settings" id="adobe-workfront-settings"></a>

| Field                      | Value                                              |
| -------------------------- | -------------------------------------------------- |
| Server URL                 | `https://mcp.workfront.adobe.com/mcp/v1/workfront` |
| Transport                  | **Streamable HTTP (recommended)**                  |
| Authentication             | **OAuth — Per-user**                               |
| Auto-discover (MCP-native) | On                                                 |

### Access and usage <a href="#adobe-workfront-access-and-usage" id="adobe-workfront-access-and-usage"></a>

Sign in with your Adobe ID and choose the intended profile and Workfront instance. Each connection targets one instance. Disconnect and reconnect to select a different one.

### Check <a href="#adobe-workfront-check" id="adobe-workfront-check"></a>

“Find one existing Workfront project and return its name and status. Do not update it or approve anything.”

### Troubleshooting <a href="#adobe-workfront-troubleshooting" id="adobe-workfront-troubleshooting"></a>

| Problem                         | What to check                                          |
| ------------------------------- | ------------------------------------------------------ |
| MCP access is disabled          | Ask the Workfront administrator to check MCP settings. |
| Redirect is rejected            | Check the exact authorized callback.                   |
| Reading works but writing fails | Check Write MCP tools and allowed actions.             |
| The wrong instance is connected | Disconnect and reconnect to the intended instance.     |

### Further information <a href="#adobe-workfront-further-information" id="adobe-workfront-further-information"></a>

* [Official documentation](https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/configure-workfront-mcp-server)

[Back to the connector index](#connector-index)

## Ahrefs <a href="#ahrefs" id="ahrefs"></a>

### What you need <a href="#ahrefs-requirements" id="ahrefs-requirements"></a>

An Ahrefs account on Lite or above, with access to the intended workspace. MCP requests consume API units from your plan.

### Prepare the service <a href="#ahrefs-setup" id="ahrefs-setup"></a>

Check your API allowance under **Account settings → Limits and usage**. This OAuth connection needs no manually supplied API key or app registration. Choose the intended workspace during sign-in and review consent. An administrator can manage the usage limit of the generated MCP key.

### Settings <a href="#ahrefs-settings" id="ahrefs-settings"></a>

| Field                      | Value                            |
| -------------------------- | -------------------------------- |
| Server URL                 | `https://api.ahrefs.com/mcp/mcp` |
| Transport                  | Streamable HTTP (recommended)    |
| Authentication             | OAuth — Per-user                 |
| Auto-discover (MCP-native) | On                               |

### Check the connection <a href="#ahrefs-check" id="ahrefs-check"></a>

Ask the assistant: “Read the available Ahrefs information for \[own website]. Give a brief summary without starting a large export.”

### Troubleshooting <a href="#ahrefs-troubleshooting" id="ahrefs-troubleshooting"></a>

| Problem                                  | What to check                                                   |
| ---------------------------------------- | --------------------------------------------------------------- |
| Sign-in succeeds but no data is returned | Check your plan, workspace, and remaining API allowance.        |
| A query stops early                      | Request fewer results; row limits and usage limits still apply. |

### More information <a href="#ahrefs-sources" id="ahrefs-sources"></a>

* [Ahrefs — setup](https://docs.ahrefs.com/en/mcp/docs/introduction)
* [Ahrefs — reference](https://docs.ahrefs.com/en/mcp/docs/chatgpt-web)

[Back to connector overview](#connector-index)

## Airtable <a href="#airtable" id="airtable"></a>

### What you need <a href="#airtable-requirements" id="airtable-requirements"></a>

An Airtable account with access to the required bases. Your Airtable role determines whether you can read or also edit.

### Prepare the service <a href="#airtable-setup" id="airtable-setup"></a>

Ask the Airtable administrator to allow the integration if third-party access is restricted. Sign in and select only the bases you need. Adjust that selection later under **Integrations → Third-party integrations**. Automatic OAuth uses dynamic client registration; do not enter separate app credentials.

### Settings <a href="#airtable-settings" id="airtable-settings"></a>

| Field                      | Value                          |
| -------------------------- | ------------------------------ |
| Server URL                 | `https://mcp.airtable.com/mcp` |
| Transport                  | Streamable HTTP (recommended)  |
| Authentication             | OAuth — Per-user               |
| Auto-discover (MCP-native) | On                             |

### Check the connection <a href="#airtable-check" id="airtable-check"></a>

Ask the assistant: “Show the names of up to three tables in \[base name]. Do not retrieve complete datasets or change anything.”

### Troubleshooting <a href="#airtable-troubleshooting" id="airtable-troubleshooting"></a>

| Problem                                     | What to check                                                                                              |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| A base is missing                           | Check both your Airtable access and the third-party integration selection.                                 |
| OAuth reports an invalid client or callback | Use automatic discovery with dynamic client registration and check the administrator’s integration policy. |

### More information <a href="#airtable-sources" id="airtable-sources"></a>

* [Airtable — setup](https://support.airtable.com/articles/9897799762-using-the-airtable-mcp-server)

[Back to connector overview](#connector-index)

## Amplitude <a href="#amplitude" id="amplitude"></a>

### What you need <a href="#amplitude-requirements" id="amplitude-requirements"></a>

An Amplitude account with access to the intended organization and projects. Your administrator must permit MCP use.

### Prepare the service <a href="#amplitude-setup" id="amplitude-setup"></a>

Use the server address associated with your Amplitude account. In addition to the prefilled address, `https://mcp.eu.amplitude.com/mcp` is available; ask your administrator which to use. Sign in with your own account. Your role controls access, and writes require the corresponding MCP write permission.

### Settings <a href="#amplitude-settings" id="amplitude-settings"></a>

| Field                      | Value                           |
| -------------------------- | ------------------------------- |
| Server URL                 | `https://mcp.amplitude.com/mcp` |
| Transport                  | Streamable HTTP (recommended)   |
| Authentication             | OAuth — Per-user                |
| Auto-discover (MCP-native) | On                              |

### Check the connection <a href="#amplitude-check" id="amplitude-check"></a>

Ask the assistant: “List the Amplitude projects I can view. Do not create a chart, cohort, or experiment.”

### Troubleshooting <a href="#amplitude-troubleshooting" id="amplitude-troubleshooting"></a>

| Problem                           | What to check                                                                                                            |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| The intended projects are missing | Check your account, server address, and project permissions.                                                             |
| A change is refused               | Check the MCP write permission. The connector does not publish guides or surveys and is not an event-ingestion endpoint. |

### More information <a href="#amplitude-sources" id="amplitude-sources"></a>

* [Amplitude — setup](https://amplitude.com/docs/amplitude-ai/amplitude-mcp)
* [Amplitude — reference](https://amplitude.com/docs/en/amplitude-ai/amplitude-mcp/other-clients)

[Back to connector overview](#connector-index)

## Artific Docs <a href="#artific-docs" id="artific-docs"></a>

### Preparation <a href="#artific-docs-preparation" id="artific-docs-preparation"></a>

No external account, API key or OAuth application is required. An organization administrator adds the connector and makes it available to the intended assistant.

### Settings <a href="#artific-docs-settings" id="artific-docs-settings"></a>

| Field          | Value                                  |
| -------------- | -------------------------------------- |
| Server URL     | `https://docs.artific.nl/~gitbook/mcp` |
| Transport      | **Streamable HTTP (recommended)**      |
| Authentication | **None**                               |

### Check <a href="#artific-docs-check" id="artific-docs-check"></a>

“Find the Artific documentation about configuring an assistant and return a short explanation with source links.”

### Troubleshooting <a href="#artific-docs-troubleshooting" id="artific-docs-troubleshooting"></a>

| Problem                  | What to check                                                       |
| ------------------------ | ------------------------------------------------------------------- |
| A sign-in window appears | Check that Authentication is None.                                  |
| No actions are available | Refresh the connector and check the organization’s allowed actions. |

### Further information <a href="#artific-docs-further-information" id="artific-docs-further-information"></a>

* [Official documentation](https://docs.artific.nl)

[Back to the connector index](#connector-index)

## Artific Outlook Mail & Calendar <a href="#artific-outlook" id="artific-outlook"></a>

### Preparation <a href="#artific-outlook-preparation" id="artific-outlook-preparation"></a>

#### Obtain or register the client application <a href="#artific-outlook-mail-and-calendar-obtain-or-register-the-client-application" id="artific-outlook-mail-and-calendar-obtain-or-register-the-client-application"></a>

Ask your integration administrator for the existing application credentials first. End users do not need to register another application when the integration administrator has already done this.

If a new registration is needed, open Microsoft Entra → App registrations → New registration. Choose an appropriate name and account type. For an application used by multiple Microsoft 365 organizations, choose multiple Entra tenants. Include personal Microsoft accounts only if the integration needs them. If using a single-tenant application, have the integration administrator set both Artific OAuth endpoints to that tenant instead of the prefilled common endpoints.

Under Authentication, add a Web redirect URI matching the Artific address you use, followed by `/oauth/callback`. For the standard Artific address, use `https://app.artific.nl/oauth/callback`. Record the Application (client) ID, not the Object ID or Directory ID.

#### Configure Microsoft permissions and credentials <a href="#artific-outlook-mail-and-calendar-configure-microsoft-permissions-and-credentials" id="artific-outlook-mail-and-calendar-configure-microsoft-permissions-and-credentials"></a>

Under API permissions → Add a permission → Microsoft Graph → Delegated permissions, configure `User.Read`, `Mail.Read`, `Mail.Send`, `Calendars.ReadWrite` and `offline_access` for the full connection. These are permissions on behalf of the signed-in user, not application permissions. Have the Microsoft administrator review any required admin consent.

For the current client-secret form, create a secret under Certificates & secrets → Client secrets. Store its Value and expiry date securely. The Secret ID is not the secret value.

### Settings <a href="#artific-outlook-settings" id="artific-outlook-settings"></a>

| Field                      | Value                                                            |
| -------------------------- | ---------------------------------------------------------------- |
| Server URL                 | `https://outlook.mcps.artific.nl/mcp`                            |
| Transport                  | **Streamable HTTP (recommended)**                                |
| Authentication             | **OAuth — Per-user**                                             |
| Auto-discover (MCP-native) | Off                                                              |
| Authorization endpoint     | `https://login.microsoftonline.com/common/oauth2/v2.0/authorize` |
| Token endpoint             | `https://login.microsoftonline.com/common/oauth2/v2.0/token`     |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#artific-outlook-scopes" id="artific-outlook-scopes"></a>

Enter the following space-separated scopes, matching the application setup:

```
offline_access User.Read Mail.Read Mail.Send Calendars.ReadWrite
```

### Access and usage <a href="#artific-outlook-access-and-usage" id="artific-outlook-access-and-usage"></a>

Enter the Application (client) ID and client secret Value from the same registration. The full scope list permits sending mail and changing calendars. For a reading-only integration, have the administrator align both the requested Microsoft permissions and the allowed actions; disabling an Artific action does not change an existing Microsoft grant.

### Check <a href="#artific-outlook-check" id="artific-outlook-check"></a>

“List my calendars and read only the subject of one recent email. Do not send mail or create an event.”

### Troubleshooting <a href="#artific-outlook-troubleshooting" id="artific-outlook-troubleshooting"></a>

| Problem                          | What to check                                                                      |
| -------------------------------- | ---------------------------------------------------------------------------------- |
| AADSTS50011 or redirect mismatch | Check the exact Web redirect URI and the Artific domain.                           |
| invalid\_client                  | Check the client secret Value and expiry date.                                     |
| Need admin approval              | Ask the Microsoft administrator to review delegated permissions and tenant policy. |
| Email works but calendars do not | Check calendar permissions, mailbox access and the allowed actions.                |

### Further information <a href="#artific-outlook-further-information" id="artific-outlook-further-information"></a>

* [Official documentation 1](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app)
* [Official documentation 2](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-redirect-uri)
* [Official documentation 3](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-configure-app-access-web-apis)
* [Official documentation 4](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials)

[Back to the connector index](#connector-index)

## Asana <a href="#asana" id="asana"></a>

### Preparation <a href="#asana-preparation" id="asana-preparation"></a>

Use existing credentials or open the Asana developer console → Create new app and select MCP app. Store the Client ID and secret. Under OAuth, register `https://app.artific.nl/oauth/callback`, or the callback on your Artific domain.

Under Manage distribution, select Specific workspaces and add the intended workspace, or Any workspace when appropriate. Save changes. An empty Specific workspaces list does not make the app available to your workspace.

### Settings <a href="#asana-settings" id="asana-settings"></a>

| Field                      | Value                                     |
| -------------------------- | ----------------------------------------- |
| Server URL                 | `https://mcp.asana.com/v2/mcp`            |
| Transport                  | **Streamable HTTP (recommended)**         |
| Authentication             | **OAuth — Per-user**                      |
| Auto-discover (MCP-native) | Off                                       |
| Authorization endpoint     | `https://app.asana.com/-/oauth_authorize` |
| Token endpoint             | `https://app.asana.com/-/oauth_token`     |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#asana-scopes" id="asana-scopes"></a>

Leave **Scopes** empty.

### Access and usage <a href="#asana-access-and-usage" id="asana-access-and-usage"></a>

Leave Scopes empty. Asana MCP apps do not require individual scopes. Use MCP-app credentials rather than a regular API application or the deprecated SSE endpoint. The connection inherits the user’s Asana permissions.

### Check <a href="#asana-check" id="asana-check"></a>

“Read one existing task in \[project] and show its title and status. Do not change it.”

### Troubleshooting <a href="#asana-troubleshooting" id="asana-troubleshooting"></a>

| Problem                                     | What to check                                                   |
| ------------------------------------------- | --------------------------------------------------------------- |
| This app is not available to your workspace | Add the workspace under Manage distribution.                    |
| Invalid scope(s) requested                  | Clear Scopes and reconnect.                                     |
| invalid\_client or redirect mismatch        | Check that credentials and callback belong to the same MCP app. |

### Further information <a href="#asana-further-information" id="asana-further-information"></a>

* [Official documentation](https://developers.asana.com/docs/integrating-with-asanas-mcp-server)

[Back to the connector index](#connector-index)

## Attio <a href="#attio" id="attio"></a>

### What you need <a href="#attio-requirements" id="attio-requirements"></a>

An Attio account in the intended workspace. Attio documents the connector as available on all plans.

### Prepare the service <a href="#attio-setup" id="attio-setup"></a>

No API key or custom OAuth app is required. Sign in with the Attio account for the intended workspace. Existing record, list, and user permissions remain in effect. Review allowed shared actions under **Manage actions**; tool read/write annotations do not replace that decision.

### Settings <a href="#attio-settings" id="attio-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.attio.com/mcp`   |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#attio-check" id="attio-check"></a>

Ask the assistant: “Find \[company name] in Attio and return only its name and current status. Do not add a note or task.”

### Troubleshooting <a href="#attio-troubleshooting" id="attio-troubleshooting"></a>

| Problem                                | What to check                                                             |
| -------------------------------------- | ------------------------------------------------------------------------- |
| A record or list is missing            | Check the workspace and whether the same account can open it in Attio.    |
| More actions are available than needed | Ask the organization administrator to disable unnecessary shared actions. |

### More information <a href="#attio-sources" id="attio-sources"></a>

* [Attio — setup](https://attio.com/help/reference/attio-ai/attio-mcp)
* [Attio — reference](https://docs.attio.com/mcp/overview)

[Back to connector overview](#connector-index)

## Box <a href="#box" id="box"></a>

### What you need <a href="#box-requirements" id="box-requirements"></a>

A Box account with access to the required content and a Box administrator who can configure the MCP integration.

### Prepare the service <a href="#box-setup" id="box-setup"></a>

1. In **Box Admin Console → Integrations**, find **Box MCP server** and choose **Configure**.
2. Under **Additional Configuration → + Add Integration Credentials**, create an integration. Copy its **Client ID** and **Client Secret** into the designated Artific fields.
3. Register `https://app.artific.nl/oauth/callback` as the **Redirect URI**, or the same route on your own Artific domain.
4. Select the required **Access Scopes** and make the integration available. This preset uses `root_readwrite` for content actions. Add Box AI or document-generation permissions only when required and available.
5. Each user signs in with their own Box account.

### Settings <a href="#box-settings" id="box-settings"></a>

| Field                      | Value                                          |
| -------------------------- | ---------------------------------------------- |
| Server URL                 | `https://mcp.box.com`                          |
| Transport                  | Streamable HTTP (recommended)                  |
| Authentication             | OAuth — Per-user                               |
| Auto-discover (MCP-native) | Off                                            |
| Authorization endpoint     | `https://account.box.com/api/oauth2/authorize` |
| Token endpoint             | `https://api.box.com/oauth2/token`             |
| Scopes                     | `root_readwrite`                               |

### Check the connection <a href="#box-check" id="box-check"></a>

Ask the assistant: “Show only the names of up to three items in my Box root folder. Do not upload, move, or share anything.”

### Troubleshooting <a href="#box-troubleshooting" id="box-troubleshooting"></a>

| Problem                              | What to check                                                                             |
| ------------------------------------ | ----------------------------------------------------------------------------------------- |
| OAuth rejects the client or callback | Use Integration Credentials from the MCP integration and check the exact Redirect URI.    |
| An action is missing                 | Check Box scopes and administrator-enabled MCP tools; some tools are disabled by default. |

### More information <a href="#box-sources" id="box-sources"></a>

* [Box — setup](https://developer.box.com/guides/box-mcp/index)
* [Box — reference](https://developer.box.com/guides/box-mcp/setup)

[Back to connector overview](#connector-index)

## Brevo <a href="#brevo" id="brevo"></a>

### What you need <a href="#brevo-requirements" id="brevo-requirements"></a>

A Brevo account and permission to generate an MCP token. Required features must be available in your Brevo setup.

### Prepare the service <a href="#brevo-setup" id="brevo-setup"></a>

In Brevo, open **Account → SMTP & API → API Keys** and generate a token with the **MCP** option. Store it in your password manager. Enter only its value in Artific’s **Bearer token** field. This connector uses Brevo’s general token-authenticated MCP endpoint; do not use an SMTP password. The shared connector acts with the token’s permissions.

### Settings <a href="#brevo-settings" id="brevo-settings"></a>

| Field          | Value                                |
| -------------- | ------------------------------------ |
| Server URL     | `https://mcp.brevo.com/v1/brevo/mcp` |
| Transport      | Streamable HTTP (recommended)        |
| Authentication | Bearer token                         |

### Check the connection <a href="#brevo-check" id="brevo-check"></a>

Ask the assistant: “Read my Brevo account information and contact count. Do not send email, SMS, or WhatsApp messages or change a campaign.”

### Troubleshooting <a href="#brevo-troubleshooting" id="brevo-troubleshooting"></a>

| Problem               | What to check                                                                          |
| --------------------- | -------------------------------------------------------------------------------------- |
| The token is rejected | Check that it is an MCP token rather than an SMTP password.                            |
| A feature is missing  | Check your Brevo plan and whether the required module and shared action are available. |

### More information <a href="#brevo-sources" id="brevo-sources"></a>

* [Brevo — setup](https://developers.brevo.com/docs/mcp-protocol)
* [Brevo — reference](https://developers.brevo.com/docs/integration-guide)

[Back to connector overview](#connector-index)

## Cal.com <a href="#cal-com" id="cal-com"></a>

### What you need <a href="#cal-com-requirements" id="cal-com-requirements"></a>

A Cal.com account with the calendars, availability, and event types you want to use. Access to teammates requires appropriate team permissions.

### Prepare the service <a href="#cal-com-setup" id="cal-com-setup"></a>

First check the calendars and event types connected to your Cal.com account. Then sign in through the connector; no API key or custom OAuth app is required. Bookings and availability follow that account’s setup. Agree when the assistant must obtain approval before creating or changing a booking.

### Settings <a href="#cal-com-settings" id="cal-com-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.cal.com/mcp`     |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#cal-com-check" id="cal-com-check"></a>

Ask the assistant: “Show my available Cal.com event types and their durations. Do not hold or book a time slot.”

### Troubleshooting <a href="#cal-com-troubleshooting" id="cal-com-troubleshooting"></a>

| Problem                     | What to check                                                                          |
| --------------------------- | -------------------------------------------------------------------------------------- |
| No times are returned       | Check connected calendars, availability rules, and the selected event type in Cal.com. |
| A colleague cannot be found | Check team membership and your permission to see that person.                          |

### More information <a href="#cal-com-sources" id="cal-com-sources"></a>

* [Cal.com — setup](https://site.cal.com/mcp)

[Back to connector overview](#connector-index)

## Calendly <a href="#calendly" id="calendly"></a>

### What you need <a href="#calendly-requirements" id="calendly-requirements"></a>

A Calendly account with the intended event types and availability. Available features depend on your Calendly permissions and plan.

### Prepare the service <a href="#calendly-setup" id="calendly-setup"></a>

Check your calendar setup in Calendly. Keep **Auto-discover (MCP-native)** enabled. Calendly registers the OAuth client automatically; do not supply a manual Client ID, client secret, or personal access token. Sign in and review access. MCP permissions also cover scheduling and changes, so agree which booking actions the assistant may perform.

### Settings <a href="#calendly-settings" id="calendly-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.calendly.com`    |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#calendly-check" id="calendly-check"></a>

Ask the assistant: “Show the names and durations of my Calendly event types. Do not create a booking or a single-use scheduling link.”

### Troubleshooting <a href="#calendly-troubleshooting" id="calendly-troubleshooting"></a>

| Problem                                 | What to check                                                                            |
| --------------------------------------- | ---------------------------------------------------------------------------------------- |
| Sign-in asks for manual app credentials | Check that automatic discovery is enabled; this server uses dynamic client registration. |
| The connection is refused               | Check that the callback for the Artific domain is an exact HTTPS URL.                    |

### More information <a href="#calendly-sources" id="calendly-sources"></a>

* [Calendly — setup](https://developer.calendly.com/docs/mcp/calendly-mcp-server)

[Back to connector overview](#connector-index)

## Canva <a href="#canva" id="canva"></a>

### Preparation <a href="#canva-preparation" id="canva-preparation"></a>

Ask the integration administrator for existing Canva MCP application credentials first. If a new application is needed, use Canva Developer Portal → Outside Canva → Start integrating, then enable Canva MCP under Integration methods.

Copy the Client ID from Credentials and use Generate secret to create a client secret. Store it securely. Under Redirect URLs, register `https://app.artific.nl/oauth/callback`, or the callback on your Artific domain. Users subsequently sign in to their own Canva account; the app credentials identify the integration.

### Settings <a href="#canva-settings" id="canva-settings"></a>

| Field                      | Value                                       |
| -------------------------- | ------------------------------------------- |
| Server URL                 | `https://api.canva.com/connect/v1/mcp`      |
| Transport                  | **Streamable HTTP (recommended)**           |
| Authentication             | **OAuth — Per-user**                        |
| Auto-discover (MCP-native) | Off                                         |
| Authorization endpoint     | `https://www.canva.com/api/oauth/authorize` |
| Token endpoint             | `https://api.canva.com/auth/v1/oauth/token` |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#canva-scopes" id="canva-scopes"></a>

Enter the following space-separated scopes, matching the application setup:

```
profile:read design:meta:read design:content:write design:content:read folder:read folder:write brandtemplate:content:read brandtemplate:meta:read brandtemplate:content:write comment:write comment:read asset:read asset:write brandkit:read help:answers:read help:answers:write
```

### Access and usage <a href="#canva-access-and-usage" id="canva-access-and-usage"></a>

The full definition includes design, folder, comment and asset editing permissions. Have the administrator align the scopes with the intended functions. Users authorize individually, and their own Canva permissions and plan govern available designs and features. Some brand, template and resize features need a higher plan.

### Check <a href="#canva-check" id="canva-check"></a>

“Find my Canva design titled \[title] and return its edit link. Do not edit or export it.”

### Troubleshooting <a href="#canva-troubleshooting" id="canva-troubleshooting"></a>

| Problem              | What to check                                            |
| -------------------- | -------------------------------------------------------- |
| invalid\_client      | Check the credentials of the app with Canva MCP enabled. |
| Redirect is rejected | Check the exact registered redirect URL.                 |
| A design is missing  | Check the signed-in account and sharing permissions.     |

### Further information <a href="#canva-further-information" id="canva-further-information"></a>

* [Official documentation 1](https://www.canva.dev/blog/developers/canva-mcp-ga/)
* [Official documentation 2](https://www.canva.dev/docs/apps/mcp/access/)

[Back to the connector index](#connector-index)

## ClickUp <a href="#clickup" id="clickup"></a>

### Preparation <a href="#clickup-preparation" id="clickup-preparation"></a>

Use a ClickUp account with access to the intended Workspace. No personal API key or separately registered application is needed for this OAuth connection. Select the intended Workspaces during authorization. ClickUp makes MCP available across its plans, with usage limits depending on the Workspace plan and any relevant AI add-on.

### Settings <a href="#clickup-settings" id="clickup-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.clickup.com/mcp`     |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Check <a href="#clickup-check" id="clickup-check"></a>

“Show the connected ClickUp Workspace name and one existing list. Do not change tasks.”

### Troubleshooting <a href="#clickup-troubleshooting" id="clickup-troubleshooting"></a>

| Problem                        | What to check                                                                    |
| ------------------------------ | -------------------------------------------------------------------------------- |
| A Workspace or task is missing | Check the Workspaces selected during authorization and your ClickUp permissions. |
| RATE\_LIMIT\_EXCEEDED          | Wait until the time indicated by ClickUp. Reconnecting does not reset the limit. |

### Further information <a href="#clickup-further-information" id="clickup-further-information"></a>

* [Official documentation](https://developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server)

[Back to the connector index](#connector-index)

## Cloudflare <a href="#cloudflare" id="cloudflare"></a>

### Preparation <a href="#cloudflare-preparation" id="cloudflare-preparation"></a>

Use an account with access to the intended Cloudflare accounts and zones. Select the intended account and review the requested access during authorization. You do not need to deploy a Worker or install a separate server for this connection.

### Settings <a href="#cloudflare-settings" id="cloudflare-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.cloudflare.com/mcp`  |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#cloudflare-access-and-usage" id="cloudflare-access-and-usage"></a>

This endpoint uses a search-and-execute pattern: a small number of actions can expose many API operations. A short action list is expected. Consider the capabilities of an execution action when choosing allowed actions.

### Check <a href="#cloudflare-check" id="cloudflare-check"></a>

“Find the Cloudflare accounts I can access and return their names only. Do not make changes.”

### Troubleshooting <a href="#cloudflare-troubleshooting" id="cloudflare-troubleshooting"></a>

| Problem                       | What to check                                        |
| ----------------------------- | ---------------------------------------------------- |
| Only a few actions appear     | This is normal for the search-and-execute interface. |
| An account or zone is missing | Check the connected account and its Cloudflare role. |

### Further information <a href="#cloudflare-further-information" id="cloudflare-further-information"></a>

* [Official documentation](https://developers.cloudflare.com/agents/model-context-protocol/cloudflare/servers-for-cloudflare/)

[Back to the connector index](#connector-index)

## Datadog <a href="#datadog" id="datadog"></a>

### What you need <a href="#datadog-requirements" id="datadog-requirements"></a>

A Datadog account with the required product permissions and **MCP Read**. Your organization administrator must allow **MCP Access**.

### Prepare the service <a href="#datadog-setup" id="datadog-setup"></a>

Ask your administrator which MCP address belongs to your account; for example, `https://mcp.datadoghq.eu/v1/mcp` is an alternative to the prefilled address. Change **Server URL** before connecting when needed. Sign in with your own account. Changes additionally require **MCP Write Access** and appropriate role permissions. Leave writing disabled for investigation-only use.

### Settings <a href="#datadog-settings" id="datadog-settings"></a>

| Field                      | Value                              |
| -------------------------- | ---------------------------------- |
| Server URL                 | `https://mcp.datadoghq.com/v1/mcp` |
| Transport                  | Streamable HTTP (recommended)      |
| Authentication             | OAuth — Per-user                   |
| Auto-discover (MCP-native) | On                                 |

### Check the connection <a href="#datadog-check" id="datadog-check"></a>

Ask the assistant: “Show the name and status of one Datadog monitor. Do not change a monitor or start an investigation that changes settings.”

### Troubleshooting <a href="#datadog-troubleshooting" id="datadog-troubleshooting"></a>

| Problem                          | What to check                                                                                                              |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Access is refused                | Check the server address, MCP Access, MCP Read, product permissions, and any network restrictions with your administrator. |
| Reading works but changes do not | Check whether writing is intentionally disabled; both organization and role permissions are required.                      |

### More information <a href="#datadog-sources" id="datadog-sources"></a>

* [Datadog — setup](https://docs.datadoghq.com/mcp_server/setup/)

[Back to connector overview](#connector-index)

## Exa <a href="#exa-search" id="exa-search"></a>

### Preparation <a href="#exa-search-preparation" id="exa-search-preparation"></a>

Open the Exa dashboard, select the team that should own the usage, and create or retrieve a dedicated API key. Store it in your password manager and check the team’s usage limits. This Marketplace entry uses a static key in the `x-api-key` header.

### Settings <a href="#exa-search-settings" id="exa-search-settings"></a>

| Field                  | Value                             |
| ---------------------- | --------------------------------- |
| Server URL             | `https://mcp.exa.ai/mcp`          |
| Transport              | **Streamable HTTP (recommended)** |
| Authentication         | **Bearer token**                  |
| Auth header (optional) | `x-api-key`                       |

### Access and usage <a href="#exa-search-access-and-usage" id="exa-search-access-and-usage"></a>

Enter only the key in Bearer token, without a Bearer prefix. Keep Auth header set to `x-api-key`. Exa also offers other authentication methods; this page describes the key-based Marketplace entry. Requests use the team and limits associated with that key.

### Check <a href="#exa-search-check" id="exa-search-check"></a>

“Search the official Artific website for product information and return up to three source links.”

### Troubleshooting <a href="#exa-search-troubleshooting" id="exa-search-troubleshooting"></a>

| Problem                  | What to check                           |
| ------------------------ | --------------------------------------- |
| The key is rejected      | Check the key and the x-api-key header. |
| A usage limit is reached | Check the Exa team’s available usage.   |

### Further information <a href="#exa-search-further-information" id="exa-search-further-information"></a>

* [Official documentation](https://exa.ai/docs/get-started/exa-mcp)

[Back to the connector index](#connector-index)

## Figma <a href="#figma" id="figma"></a>

### Preparation <a href="#figma-preparation" id="figma-preparation"></a>

Figma requires approved MCP clients. Have the Artific integration administrator confirm that Artific has been approved, or submit Artific through the client waitlist linked in Figma’s official guide. An ordinary Figma account, OAuth application or personal access token does not replace client approval. The remote connection does not require the desktop application.

### Settings <a href="#figma-settings" id="figma-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.figma.com/mcp`       |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#figma-access-and-usage" id="figma-access-and-usage"></a>

Provide a file or frame-selection link. The remote connection does not use the current selection in a local desktop application. The connected account must be able to open that file.

### Check <a href="#figma-check" id="figma-check"></a>

“Read the design context for this Figma frame link: \[link]. Describe the layout and components without editing.”

### Troubleshooting <a href="#figma-troubleshooting" id="figma-troubleshooting"></a>

| Problem                         | What to check                                                      |
| ------------------------------- | ------------------------------------------------------------------ |
| Artific is rejected as a client | Have the integration administrator complete Figma client approval. |
| A frame cannot be read          | Check the file link, node ID and file access.                      |
| A limit is reached              | Check Figma plan and usage limits.                                 |

### Further information <a href="#figma-further-information" id="figma-further-information"></a>

* [Official documentation](https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/)

[Back to the connector index](#connector-index)

## Fireflies <a href="#fireflies" id="fireflies"></a>

### Preparation <a href="#fireflies-preparation" id="fireflies-preparation"></a>

Use a Fireflies account that can already open the intended meetings. Have at least one processed recording available for your first check. This OAuth entry does not require an API key. Choose the sign-in method associated with the correct Fireflies account, including Google or Microsoft if applicable.

### Settings <a href="#fireflies-settings" id="fireflies-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://api.fireflies.ai/mcp`    |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Check <a href="#fireflies-check" id="fireflies-check"></a>

“List the title and date of my most recent available meeting. Do not retrieve the full transcript.”

### Troubleshooting <a href="#fireflies-troubleshooting" id="fireflies-troubleshooting"></a>

| Problem                     | What to check                                                                               |
| --------------------------- | ------------------------------------------------------------------------------------------- |
| No meetings appear          | Check the account, recording processing and sharing permissions in Fireflies.               |
| A team recording is missing | Team membership alone does not grant access to every recording; check its sharing settings. |

### Further information <a href="#fireflies-further-information" id="fireflies-further-information"></a>

* [Official documentation](https://guide.fireflies.ai/articles/8272956938-learn-about-the-fireflies-mcp-server-model-context-protocol)

[Back to the connector index](#connector-index)

## GitHub <a href="#github" id="github"></a>

### Preparation <a href="#github-preparation" id="github-preparation"></a>

1. In GitHub, open Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.
2. Set a descriptive name and expiry date.
3. Select the intended Resource owner and restrict Repository access to the required repositories.
4. Grant the permissions your task needs, such as Contents: Read-only for code and the relevant reading permissions for issues or pull requests.
5. Obtain organization approval if required and store the token securely.

### Settings <a href="#github-settings" id="github-settings"></a>

| Field                  | Value                               |
| ---------------------- | ----------------------------------- |
| Server URL             | `https://api.githubcopilot.com/mcp` |
| Transport              | **Streamable HTTP (recommended)**   |
| Authentication         | **Bearer token**                    |
| Auth header (optional) | Leave empty                         |

### Access and usage <a href="#github-access-and-usage" id="github-access-and-usage"></a>

The token is tied to its owner and selected repository permissions. Everyone using this shared connection acts with that token’s access. For a long-lived organization integration, ask your administrator to assess a GitHub App configuration; that is a different setup from this token-based entry.

### Check <a href="#github-check" id="github-check"></a>

“Read the README of \[owner/repository] and summarize it. Do not change files or create a pull request.”

### Troubleshooting <a href="#github-troubleshooting" id="github-troubleshooting"></a>

| Problem                      | What to check                                                             |
| ---------------------------- | ------------------------------------------------------------------------- |
| A repository is missing      | Check the Resource owner, repository selection and organization approval. |
| 403 or an expired connection | Check token permissions, expiry, SSO and organization token policy.       |

### Further information <a href="#github-further-information" id="github-further-information"></a>

* [Official documentation 1](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)
* [Official documentation 2](https://github.com/github/github-mcp-server/blob/main/docs/remote-server.md)

[Back to the connector index](#connector-index)

## GitLab <a href="#gitlab" id="gitlab"></a>

### What you need <a href="#gitlab-requirements" id="gitlab-requirements"></a>

A GitLab account with access to the required projects. An administrator must permit MCP for the relevant group or self-managed instance.

### Prepare the service <a href="#gitlab-setup" id="gitlab-setup"></a>

The preset uses GitLab.com. For a self-managed instance, change the address to `https://[own-gitlab-domain]/api/v4/mcp`. Keep automatic discovery enabled when dynamic client registration is allowed. Sign in with your own account. Do not substitute a personal access token: the documented MCP flow requires an OAuth token with the `mcp` scope.

### Settings <a href="#gitlab-settings" id="gitlab-settings"></a>

| Field                      | Value                           |
| -------------------------- | ------------------------------- |
| Server URL                 | `https://gitlab.com/api/v4/mcp` |
| Transport                  | Streamable HTTP (recommended)   |
| Authentication             | OAuth — Per-user                |
| Auto-discover (MCP-native) | On                              |

### Check the connection <a href="#gitlab-check" id="gitlab-check"></a>

Ask the assistant: “Read the title and status of GitLab issue \[project path and issue number]. Do not create an issue, commit, or merge request.”

### Troubleshooting <a href="#gitlab-troubleshooting" id="gitlab-troubleshooting"></a>

| Problem                            | What to check                                                                                                                    |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Sign-in or registration is refused | Check whether MCP and dynamic client registration are allowed. Disabled registration requires a separately configured OAuth app. |
| A project or tool is missing       | Check project permissions, enabled toolsets, and the features of your GitLab version.                                            |

### More information <a href="#gitlab-sources" id="gitlab-sources"></a>

* [GitLab — setup](https://docs.gitlab.com/user/model_context_protocol/mcp_server/)

[Back to connector overview](#connector-index)

## HiBob <a href="#hibob" id="hibob"></a>

### Preparation <a href="#hibob-preparation" id="hibob-preparation"></a>

Ask the Bob administrator to enable Bob MCP and review the employee’s permissions and available modules. Administration instructions are in the Bob Help Center under Manage Bob MCP. Use OAuth rather than creating a service user: HiBob has blocked new legacy service-user connections since 9 November 2026.

### Settings <a href="#hibob-settings" id="hibob-settings"></a>

| Field                      | Value                              |
| -------------------------- | ---------------------------------- |
| Server URL                 | `https://mcp.hibob.com/mcp/public` |
| Transport                  | **Streamable HTTP (recommended)**  |
| Authentication             | **OAuth — Per-user**               |
| Auto-discover (MCP-native) | On                                 |

### Access and usage <a href="#hibob-access-and-usage" id="hibob-access-and-usage"></a>

Each employee connects separately. Results and available actions depend on that employee’s Bob rights and enabled modules. Use the OAuth endpoint on mcp.hibob.com.

### Check <a href="#hibob-check" id="hibob-check"></a>

“Show which Bob capabilities are available to my account. Do not retrieve colleagues’ details or make changes.”

### Troubleshooting <a href="#hibob-troubleshooting" id="hibob-troubleshooting"></a>

| Problem                                  | What to check                                                   |
| ---------------------------------------- | --------------------------------------------------------------- |
| MCP is unavailable                       | Ask the Bob administrator to check availability and activation. |
| Data or an HR action is missing          | Check Bob permissions and the relevant module.                  |
| An old guide asks for a service-user key | Use per-user OAuth with automatic discovery for this entry.     |

### Further information <a href="#hibob-further-information" id="hibob-further-information"></a>

* [Official documentation 1](https://apidocs.hibob.com/docs/hibob-mcp-server)
* [Official documentation 2](https://www.hibob.com/platform/core/ai/mcp/)

[Back to the connector index](#connector-index)

## Higgsfield <a href="#higgsfield" id="higgsfield"></a>

### Preparation <a href="#higgsfield-preparation" id="higgsfield-preparation"></a>

Use the Higgsfield account containing your assets and credits. No API key is needed for this OAuth connection. Generating through MCP consumes credits even when a model offers Unlimited or free generation on the website. Check available credits before allowing generation actions.

### Settings <a href="#higgsfield-settings" id="higgsfield-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.higgsfield.ai/mcp`   |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#higgsfield-access-and-usage" id="higgsfield-access-and-usage"></a>

Start with an available account or asset reading action. Enable generation only when needed and instruct the assistant to obtain agreement before spending credits.

### Check <a href="#higgsfield-check" id="higgsfield-check"></a>

“Show available Higgsfield account or asset information without generating media or spending credits.”

### Troubleshooting <a href="#higgsfield-troubleshooting" id="higgsfield-troubleshooting"></a>

| Problem                                   | What to check                                                          |
| ----------------------------------------- | ---------------------------------------------------------------------- |
| Generation fails but works on the website | Check credits: website Unlimited rules do not apply to MCP generation. |
| The wrong assets appear                   | Reconnect using the account containing those assets.                   |

### Further information <a href="#higgsfield-further-information" id="higgsfield-further-information"></a>

* [Official documentation](https://higgsfield.ai/creator-hub/help-center/integrations/what-is-higgsfield-mcp)

[Back to the connector index](#connector-index)

## HoorayHR <a href="#hoorayhr" id="hoorayhr"></a>

### Preparation <a href="#hoorayhr-preparation" id="hoorayhr-preparation"></a>

Use a HoorayHR account on the Plus plan. The administrator controls employee access under Bedrijfsinstellingen → Zichtbaarheid. Without employee access enabled, only administrators can use this feature. No separate OAuth application or API key is required.

### Settings <a href="#hoorayhr-settings" id="hoorayhr-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://api.hoorayhr.io/mcp`     |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#hoorayhr-access-and-usage" id="hoorayhr-access-and-usage"></a>

The documented HoorayHR MCP version currently supports reading only, even if an authorization screen mentions writing. Existing account permissions continue to apply.

### Check <a href="#hoorayhr-check" id="hoorayhr-check"></a>

“Show my own remaining leave balance. Do not submit or change a leave request.”

### Troubleshooting <a href="#hoorayhr-troubleshooting" id="hoorayhr-troubleshooting"></a>

| Problem                    | What to check                                                 |
| -------------------------- | ------------------------------------------------------------- |
| The feature is unavailable | Check the Plus plan and visibility setting.                   |
| An employee cannot connect | Ask the HoorayHR administrator to review employee MCP access. |
| Writing is unavailable     | The documented version supports reading only.                 |

### Further information <a href="#hoorayhr-further-information" id="hoorayhr-further-information"></a>

* [Official documentation](https://helpcenter.hoorayhr.io/nl/articles/16627052-hoorayhr-koppelen-aan-een-ai-assistent-mcp)

[Back to the connector index](#connector-index)

## HubSpot <a href="#hubspot" id="hubspot"></a>

### Preparation <a href="#hubspot-preparation" id="hubspot-preparation"></a>

In HubSpot, open Development → MCP Connectors → Create MCP connector. Older interfaces may call this MCP Auth Apps. Give it a name and register the Artific redirect URI: `https://app.artific.nl/oauth/callback`, or the same path on your Artific domain. Create the connector and store its Client ID and client secret. A private-app token is not a substitute for these credentials.

HubSpot determines available permissions from the MCP tools and installation consent. Review the actual access requested when the user connects. New permissions require authorization again.

### Settings <a href="#hubspot-settings" id="hubspot-settings"></a>

| Field                      | Value                                          |
| -------------------------- | ---------------------------------------------- |
| Server URL                 | `https://mcp.hubspot.com`                      |
| Transport                  | **Streamable HTTP (recommended)**              |
| Authentication             | **OAuth — Per-user**                           |
| Auto-discover (MCP-native) | Off                                            |
| Authorization endpoint     | `https://mcp.hubspot.com/oauth/authorize/user` |
| Token endpoint             | `https://mcp.hubspot.com/oauth/v3/token`       |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#hubspot-scopes" id="hubspot-scopes"></a>

Enter the following space-separated scopes, matching the application setup:

```
crm.objects.contacts.read crm.objects.companies.read
```

### Access and usage <a href="#hubspot-access-and-usage" id="hubspot-access-and-usage"></a>

The current definition requests `crm.objects.contacts.read crm.objects.companies.read`. This is not a complete list of HubSpot MCP capabilities. Align any additional access with your integration administrator. If HubSpot rejects explicit scopes, follow its current MCP flow without manually supplied scopes rather than substituting a regular API application. HubSpot can restrict activities and conversations when Sensitive Data is enabled.

### Check <a href="#hubspot-check" id="hubspot-check"></a>

“Read one existing HubSpot contact and its company name. Do not update records.”

### Troubleshooting <a href="#hubspot-troubleshooting" id="hubspot-troubleshooting"></a>

| Problem                              | What to check                                                         |
| ------------------------------------ | --------------------------------------------------------------------- |
| MCP Connectors is missing            | Check your HubSpot development and administration permissions.        |
| invalid\_client or redirect mismatch | Check that credentials and redirect belong to the same MCP connector. |
| Contacts work but activities do not  | Review Sensitive Data restrictions and available account permissions. |

### Further information <a href="#hubspot-further-information" id="hubspot-further-information"></a>

* [Official documentation](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server)

[Back to the connector index](#connector-index)

## Intercom <a href="#intercom" id="intercom"></a>

### What you need <a href="#intercom-requirements" id="intercom-requirements"></a>

An Intercom account and an administrator who can issue an API access token for the intended workspace.

### Prepare the service <a href="#intercom-setup" id="intercom-setup"></a>

Create an access token for the correct workspace in **Intercom Developer Hub**. Configure required permissions for users and companies, conversations, and help articles; include article-writing permissions only when needed. Enter the token value in **Bearer token**. Ask your administrator whether the prefilled address or `https://mcp.eu.intercom.com/mcp` matches the workspace. This token route does not need OAuth callback registration.

### Settings <a href="#intercom-settings" id="intercom-settings"></a>

| Field          | Value                          |
| -------------- | ------------------------------ |
| Server URL     | `https://mcp.intercom.com/mcp` |
| Transport      | Streamable HTTP (recommended)  |
| Authentication | Bearer token                   |

### Check the connection <a href="#intercom-check" id="intercom-check"></a>

Ask the assistant: “Find one existing Intercom conversation about \[topic] and show only its subject. Do not add a note or send a reply.”

### Troubleshooting <a href="#intercom-troubleshooting" id="intercom-troubleshooting"></a>

| Problem                  | What to check                                                                                            |
| ------------------------ | -------------------------------------------------------------------------------------------------------- |
| The token is rejected    | Check the workspace, server address, and token permissions.                                              |
| An OAuth sign-in appears | This preset uses Bearer token. A separate OAuth route requires Intercom to approve the Artific callback. |

### More information <a href="#intercom-sources" id="intercom-sources"></a>

* [Intercom — setup](https://developers.intercom.com/docs/guides/mcp)

[Back to connector overview](#connector-index)

## Jira & Confluence <a href="#atlassian" id="atlassian"></a>

### Preparation <a href="#atlassian-preparation" id="atlassian-preparation"></a>

Use an Atlassian Cloud account that can already open the intended projects and spaces. Ask the Atlassian administrator to review external MCP-client restrictions if necessary. This automatic OAuth connection does not require your own API token or OAuth application. Select the correct cloud site during authorization; Jira access does not automatically grant access to a restricted Confluence space.

### Settings <a href="#atlassian-settings" id="atlassian-settings"></a>

| Field                      | Value                              |
| -------------------------- | ---------------------------------- |
| Server URL                 | `https://mcp.atlassian.com/v2/mcp` |
| Transport                  | **Streamable HTTP (recommended)**  |
| Authentication             | **OAuth — Per-user**               |
| Auto-discover (MCP-native) | On                                 |

### Check <a href="#atlassian-check" id="atlassian-check"></a>

“Read Jira work item \[project-key-number] and return its title and status. Do not change it.”

### Troubleshooting <a href="#atlassian-troubleshooting" id="atlassian-troubleshooting"></a>

| Problem                               | What to check                                                          |
| ------------------------------------- | ---------------------------------------------------------------------- |
| Confluence content is missing         | Check the connected account’s Confluence access and space permissions. |
| The organization blocks authorization | Ask the Atlassian administrator to review the MCP-client policy.       |

### Further information <a href="#atlassian-further-information" id="atlassian-further-information"></a>

* [Official documentation](https://atlassian.github.io/atlassian-mcp-server/)

[Back to the connector index](#connector-index)

## Jortt <a href="#jortt" id="jortt"></a>

### What you need <a href="#jortt-requirements" id="jortt-requirements"></a>

A Jortt account with access to the intended administration. MCP is available from the Jortt MKB plan.

### Prepare the service <a href="#jortt-setup" id="jortt-setup"></a>

No API key or custom app registration is required. Sign in to Jortt and select the intended administration. Choose **Alleen lezen** on the consent screen for retrieval only. Choose **Lezen en schrijven** only when bookkeeping actions are required. Access can later be adjusted per module in Jortt.

### Settings <a href="#jortt-settings" id="jortt-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.jortt.nl/mcp`    |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#jortt-check" id="jortt-check"></a>

Ask the assistant: “Show my Jortt administration name and the number of outstanding invoices. Do not post entries or change an invoice.”

### Troubleshooting <a href="#jortt-troubleshooting" id="jortt-troubleshooting"></a>

| Problem                 | What to check                                                      |
| ----------------------- | ------------------------------------------------------------------ |
| An API key is requested | Check that per-user OAuth with automatic discovery is selected.    |
| An action is refused    | Check the plan, selected administration, and granted access level. |

### More information <a href="#jortt-sources" id="jortt-sources"></a>

* [Jortt — setup](https://www.jortt.nl/ai-assistent/)
* [Jortt — reference](https://www.jortt.nl/koppelingen/mcp-koppeling/)

[Back to connector overview](#connector-index)

## Klaviyo <a href="#klaviyo" id="klaviyo"></a>

### What you need <a href="#klaviyo-requirements" id="klaviyo-requirements"></a>

A Klaviyo account with a role permitted to authorize MCP. The connection guide lists Owner, Admin, or Manager.

### Prepare the service <a href="#klaviyo-setup" id="klaviyo-setup"></a>

Sign in to the Klaviyo account you intend to use. The official remote needs no private API key. For multiple accounts, use separate connectors with recognizable names. For retrieval-only use, append `?read-only=true` to **Server URL** before connecting; this limits the server’s exposed tools to reading.

### Settings <a href="#klaviyo-settings" id="klaviyo-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.klaviyo.com/mcp` |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#klaviyo-check" id="klaviyo-check"></a>

Ask the assistant: “Show the name and send date of up to three existing Klaviyo campaigns. Do not create, edit, or send a campaign.”

### Troubleshooting <a href="#klaviyo-troubleshooting" id="klaviyo-troubleshooting"></a>

| Problem                        | What to check                                                                                     |
| ------------------------------ | ------------------------------------------------------------------------------------------------- |
| The wrong account is connected | Reconnect and select the correct account; use recognizable connector names.                       |
| Actions have not appeared      | Refresh the connector after the first connection completes; initial tool loading can take longer. |

### More information <a href="#klaviyo-sources" id="klaviyo-sources"></a>

* [Klaviyo — setup](https://developers.klaviyo.com/en/docs/connect_to_the_klaviyo_mcp_server)

[Back to connector overview](#connector-index)

## Linear <a href="#linear" id="linear"></a>

### Preparation <a href="#linear-preparation" id="linear-preparation"></a>

Use a Linear account with access to the intended workspace and teams. No separate API key or application registration is needed for automatic OAuth. Select the correct workspace when authorizing.

### Settings <a href="#linear-settings" id="linear-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.linear.app/mcp`      |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#linear-access-and-usage" id="linear-access-and-usage"></a>

For a reading-only connection, change Server URL before saving to `https://mcp.linear.app/mcp/readonly`. Keep automatic discovery enabled. This server variant exposes only reading actions.

### Check <a href="#linear-check" id="linear-check"></a>

“Read one existing Linear issue and return its title, status and team. Do not change it.”

### Troubleshooting <a href="#linear-troubleshooting" id="linear-troubleshooting"></a>

| Problem                     | What to check                                                   |
| --------------------------- | --------------------------------------------------------------- |
| An issue is missing         | Check the selected workspace and team access.                   |
| Writing actions are missing | Check whether you intentionally selected the readonly endpoint. |

### Further information <a href="#linear-further-information" id="linear-further-information"></a>

* [Official documentation](https://linear.app/docs/mcp)

[Back to the connector index](#connector-index)

## Microsoft 365 Work IQ <a href="#microsoft-workiq" id="microsoft-workiq"></a>

### Preparation <a href="#microsoft-workiq-preparation" id="microsoft-workiq-preparation"></a>

#### Enable Work IQ <a href="#microsoft-workiq-enable-work-iq" id="microsoft-workiq-enable-work-iq"></a>

Have a Global Administrator follow Microsoft’s tenant-enablement guide. Check the Work IQ service principal, the usage-based Copilot Studio billing plan and the user’s assignment to that plan. A mailbox alone does not enable this integration.

#### Configure the client application <a href="#microsoft-workiq-configure-the-client-application" id="microsoft-workiq-configure-the-client-application"></a>

Use the Entra application managed by your integration administrator, or register one under Microsoft Entra → App registrations. Add a Web redirect URI of `https://app.artific.nl/oauth/callback`, or the callback on your Artific domain. Use a multitenant account type when serving multiple organizations. The prefilled organizations endpoints are for work and school accounts.

Under API permissions, configure the required delegated Work IQ permissions: WorkIQ.Read, WorkIQ.Act and WorkIQAgent.Ask for the full definition. Obtain administrator consent. Ordinary Graph email or calendar permissions do not replace Work IQ permissions.

Record the Application (client) ID. For the current client-secret configuration, create a client secret under Certificates & secrets and store its Value and expiry date. End users use the configured application; they do not each create another one.

### Settings <a href="#microsoft-workiq-settings" id="microsoft-workiq-settings"></a>

| Field                      | Value                                                                   |
| -------------------------- | ----------------------------------------------------------------------- |
| Server URL                 | `https://workiq.svc.cloud.microsoft/mcp`                                |
| Transport                  | **Streamable HTTP (recommended)**                                       |
| Authentication             | **OAuth — Per-user**                                                    |
| Auto-discover (MCP-native) | Off                                                                     |
| Authorization endpoint     | `https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize` |
| Token endpoint             | `https://login.microsoftonline.com/organizations/oauth2/v2.0/token`     |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#microsoft-workiq-scopes" id="microsoft-workiq-scopes"></a>

Enter the following space-separated scopes, matching the application setup:

```
offline_access api://workiq.svc.cloud.microsoft/WorkIQ.Read api://workiq.svc.cloud.microsoft/WorkIQ.Act api://workiq.svc.cloud.microsoft/WorkIQAgent.Ask
```

### Access and usage <a href="#microsoft-workiq-access-and-usage" id="microsoft-workiq-access-and-usage"></a>

WorkIQ.Read permits reading. WorkIQ.Act permits changes, and WorkIQAgent.Ask can also expose reading and writing through agents. For reading-only usage, align application permissions and actions with offline\_access and api://workiq.svc.cloud.microsoft/WorkIQ.Read. The organization endpoints do not support personal Outlook.com accounts.

### Check <a href="#microsoft-workiq-check" id="microsoft-workiq-check"></a>

“Find a document I can access about \[topic] and return its title and source link. Do not send messages or change Microsoft 365 data.”

### Troubleshooting <a href="#microsoft-workiq-troubleshooting" id="microsoft-workiq-troubleshooting"></a>

| Problem                        | What to check                                                           |
| ------------------------------ | ----------------------------------------------------------------------- |
| Need admin approval            | Have the tenant administrator review delegated Work IQ permissions.     |
| Work IQ is unavailable         | Check tenant enablement and the service principal.                      |
| Access is denied after sign-in | Review scopes, tenant policy, application setup and billing assignment. |
| invalid\_client                | Check the secret Value and expiry, not the Secret ID.                   |

### Further information <a href="#microsoft-workiq-further-information" id="microsoft-workiq-further-information"></a>

* [Official documentation 1](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/work-iq/mcp/overview)
* [Official documentation 2](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/work-iq/enable-work-iq)
* [Official documentation 3](https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/work-iq/permissions)
* [Official documentation 4](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app)
* [Official documentation 5](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials)

[Back to the connector index](#connector-index)

## Miro <a href="#miro" id="miro"></a>

### What you need <a href="#miro-requirements" id="miro-requirements"></a>

A Miro account with access to the required boards. On Enterprise, an administrator may first need to enable MCP for the organization or selected teams.

### Prepare the service <a href="#miro-setup" id="miro-setup"></a>

If needed, review **Admin settings → Apps & Integrations → MCP** with your Miro administrator. Then sign in and select the team containing the intended board. The connection is team-specific. Automatic OAuth requires no API key or custom app. Give the assistant the board link to identify the correct board.

### Settings <a href="#miro-settings" id="miro-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.miro.com/`       |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#miro-check" id="miro-check"></a>

Ask the assistant: “Read the frame titles on Miro board \[board link]. Do not add or change any board content.”

### Troubleshooting <a href="#miro-troubleshooting" id="miro-troubleshooting"></a>

| Problem                          | What to check                                                                     |
| -------------------------------- | --------------------------------------------------------------------------------- |
| A board returns an access error  | Reconnect and choose the team containing the board; also check board permissions. |
| Enterprise blocks the connection | Ask the administrator to enable MCP for the organization or relevant team.        |

### More information <a href="#miro-sources" id="miro-sources"></a>

* [Miro — setup](https://developers.miro.com/docs/connecting-to-miro-mcp)
* [Miro — reference](https://developers.miro.com/docs/miro-mcp-server-frequently-asked-questions)

[Back to connector overview](#connector-index)

## monday.com <a href="#monday" id="monday"></a>

### Preparation <a href="#monday-preparation" id="monday-preparation"></a>

No personal API token is required for this entry. Use an account with access to the intended workspaces and boards. If your organization restricts app installation, have a monday account administrator review the connection.

### Settings <a href="#monday-settings" id="monday-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.monday.com/mcp`      |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Check <a href="#monday-check" id="monday-check"></a>

“Show a monday workspace name and one existing board. Do not change items.”

### Troubleshooting <a href="#monday-troubleshooting" id="monday-troubleshooting"></a>

| Problem                               | What to check                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------- |
| An administrator must approve the app | Ask the monday account administrator to approve the installation and connect again.   |
| A board is missing                    | Check that the same monday user can open it.                                          |
| OAuth fails                           | Do not paste an API token into OAuth fields; this connector signs in with OAuth only. |

### Further information <a href="#monday-further-information" id="monday-further-information"></a>

* [Official documentation 1](https://support.monday.com/hc/en-us/articles/28515034903314-Get-started-with-monday-MCP)
* [Official documentation 2](https://developer.monday.com/api-reference/docs/integrate-with-monday-mcp)

[Back to the connector index](#connector-index)

## Moneybird (read-only) <a href="#moneybird-readonly" id="moneybird-readonly"></a>

### Preparation <a href="#moneybird-readonly-preparation" id="moneybird-readonly-preparation"></a>

Use a Moneybird account with access to the intended administration and permission to authorize the connection. No developer application or API token is required for this OAuth entry. Check which administration you select if your account has access to several.

### Settings <a href="#moneybird-readonly-settings" id="moneybird-readonly-settings"></a>

| Field                      | Value                                    |
| -------------------------- | ---------------------------------------- |
| Server URL                 | `https://moneybird.com/mcp/v1/read_only` |
| Transport                  | **Streamable HTTP (recommended)**        |
| Authentication             | **OAuth — Per-user**                     |
| Auto-discover (MCP-native) | On                                       |

### Access and usage <a href="#moneybird-readonly-access-and-usage" id="moneybird-readonly-access-and-usage"></a>

Keep the `/read_only` endpoint. This connection cannot create or edit invoices or contacts. Do not switch it to `/read_write` while following this guide.

### Check <a href="#moneybird-readonly-check" id="moneybird-readonly-check"></a>

“Show the connected Moneybird administration name and read one existing contact. Do not change anything.”

### Troubleshooting <a href="#moneybird-readonly-troubleshooting" id="moneybird-readonly-troubleshooting"></a>

| Problem                            | What to check                                    |
| ---------------------------------- | ------------------------------------------------ |
| The wrong administration is used   | Reconnect and review administration access.      |
| Creating or editing is unavailable | That is expected for this reading-only endpoint. |

### Further information <a href="#moneybird-readonly-further-information" id="moneybird-readonly-further-information"></a>

* [Official documentation](https://www.moneybird.nl/helpcenter/nl/articles/396511-ai-koppeling)

[Back to the connector index](#connector-index)

## Notion <a href="#notion" id="notion"></a>

### Preparation <a href="#notion-preparation" id="notion-preparation"></a>

Use an account with access to the intended workspace and content. Do not create a separate Notion API integration for this OAuth entry. If an Enterprise workspace restricts MCP clients, its owner can approve Artific under Settings → Notion MCP → Manage workspace clients, including by its OAuth redirect URL.

### Settings <a href="#notion-settings" id="notion-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.notion.com/mcp`      |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Check <a href="#notion-check" id="notion-check"></a>

“Find the Notion page titled \[title] and summarize it briefly. Do not edit it.”

### Troubleshooting <a href="#notion-troubleshooting" id="notion-troubleshooting"></a>

| Problem                | What to check                                                              |
| ---------------------- | -------------------------------------------------------------------------- |
| Disabled by admin      | Ask the workspace owner to approve Artific as an MCP client.               |
| A page cannot be found | Check the selected workspace and the connected user’s access to that page. |

### Further information <a href="#notion-further-information" id="notion-further-information"></a>

* [Official documentation](https://www.notion.com/help/notion-mcp)

[Back to the connector index](#connector-index)

## Odoo <a href="#odoo" id="odoo"></a>

### What you need <a href="#odoo-requirements" id="odoo-requirements"></a>

An Odoo database with the official MCP functionality described in the Odoo 20 documentation, and a user permitted to use the required actions. A standalone API on an older installation is not sufficient.

### Prepare the service <a href="#odoo-setup" id="odoo-setup"></a>

1. Replace the example `https://example.odoo.com/mcp` with your own database’s HTTPS URL followed by `/mcp`.
2. In Odoo, open your user menu → **My Preferences → Security → Create API Key**. Set **Scope** to **MCP** and choose an expiration date.
3. Store the key and enter only its value in Artific’s **Bearer token** field.
4. Ask the Odoo administrator to expose the required server actions as **AI tools**. Available actions and user permissions determine what the assistant can do. This preset uses the documented key-based route; OAuth is not required.

### Settings <a href="#odoo-settings" id="odoo-settings"></a>

| Field          | Value                          |
| -------------- | ------------------------------ |
| Server URL     | `https://example.odoo.com/mcp` |
| Transport      | Streamable HTTP (recommended)  |
| Authentication | Bearer token                   |

### Check the connection <a href="#odoo-check" id="odoo-check"></a>

Ask the assistant: “List the available Odoo actions and read one existing contact if an appropriate read action exists. Do not create or change anything.”

### Troubleshooting <a href="#odoo-troubleshooting" id="odoo-troubleshooting"></a>

| Problem              | What to check                                                                 |
| -------------------- | ----------------------------------------------------------------------------- |
| No actions appear    | Ask the administrator to expose the required server actions as AI tools.      |
| The connection fails | Check your own database URL, MCP support, and the key’s scope and expiration. |

### More information <a href="#odoo-sources" id="odoo-sources"></a>

* [Odoo — setup](https://www.odoo.com/documentation/20.0/applications/productivity/ai/mcp_server.html)

[Back to connector overview](#connector-index)

## Pennylane <a href="#pennylane" id="pennylane"></a>

### What you need <a href="#pennylane-requirements" id="pennylane-requirements"></a>

A Pennylane company account on Essentiel or above, or an accounting-firm account with access to the intended client files.

### Prepare the service <a href="#pennylane-setup" id="pennylane-setup"></a>

Sign in and select the intended company or firm. No API key is required. A company connection targets that company; with a firm connection, first have the assistant list accessible companies and select the intended file. The documented MCP server currently exposes read-only actions.

### Settings <a href="#pennylane-settings" id="pennylane-settings"></a>

| Field                      | Value                           |
| -------------------------- | ------------------------------- |
| Server URL                 | `https://mcp.pennylane.com/mcp` |
| Transport                  | Streamable HTTP (recommended)   |
| Authentication             | OAuth — Per-user                |
| Auto-discover (MCP-native) | On                              |

### Check the connection <a href="#pennylane-check" id="pennylane-check"></a>

Ask the assistant: “Show the selected Pennylane company name and read the total of one existing customer invoice. Do not retrieve the full ledger.”

### Troubleshooting <a href="#pennylane-troubleshooting" id="pennylane-troubleshooting"></a>

| Problem                                     | What to check                                                                                |
| ------------------------------------------- | -------------------------------------------------------------------------------------------- |
| A company is missing                        | Check account permissions and whether that company is eligible for MCP.                      |
| The assistant selects the wrong client file | For a firm connection, explicitly supply the company name or ID and have it confirmed first. |

### More information <a href="#pennylane-sources" id="pennylane-sources"></a>

* [Pennylane — setup](https://help.pennylane.com/fr/articles/757740-connecter-votre-assistant-ia-au-mcp-pennylane)
* [Pennylane — reference](https://pennylane-mcp.readme.io/docs/getting-started)

[Back to connector overview](#connector-index)

## Personio <a href="#personio" id="personio"></a>

### What you need <a href="#personio-requirements" id="personio-requirements"></a>

A Personio organization with the MCP beta activated. Personio lists Core Pro as eligible. A Personio administrator and prior approval of Artific as a custom AI client are also required.

### Prepare the service <a href="#personio-setup" id="personio-setup"></a>

1. Ask the Personio administrator to enable general AI access and **Personio MCP** under **Settings → Account & support → AI features**. Limit available tools and person attributes to those needed.
2. Ask your Personio Customer Success Manager to allow Artific as a custom AI tool. Supply the fixed callback `https://app.artific.nl/oauth/callback`, or the same route on your Artific domain, and specify a public OAuth client with PKCE and no client secret.
3. Use the Client ID Personio registers for that Artific client. Do not reuse another AI application’s client ID.
4. Enter the Client ID in Artific, leave **Client secret** empty, and disable **Auto-discover**. Each user signs in with their own Personio account.

### Settings <a href="#personio-settings" id="personio-settings"></a>

| Field                      | Value                                    |
| -------------------------- | ---------------------------------------- |
| Server URL                 | `https://app.personio.com/mcp`           |
| Transport                  | Streamable HTTP (recommended)            |
| Authentication             | OAuth — Per-user                         |
| Auto-discover (MCP-native) | Off                                      |
| Authorization endpoint     | `https://login.personio.com/authorize`   |
| Token endpoint             | `https://login.personio.com/oauth/token` |
| Scopes                     | `mcp:access`                             |

### Check the connection <a href="#personio-check" id="personio-check"></a>

Ask the assistant: “Read my own remaining Personio leave balance. Do not submit leave or retrieve salary or performance information.”

### Troubleshooting <a href="#personio-troubleshooting" id="personio-troubleshooting"></a>

| Problem                              | What to check                                                                                                                 |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| Personio MCP is not visible          | Check whether the organization’s beta has been activated.                                                                     |
| OAuth rejects the client or callback | Ask Personio to check approval, Client ID, and the exact Artific callback. Creating a Personio account alone is insufficient. |

### More information <a href="#personio-sources" id="personio-sources"></a>

* [Personio — setup](https://support.personio.de/hc/en-us/articles/38314656674333-Personio-MCP-server-Beta-access-overview)

[Back to connector overview](#connector-index)

## Pipedrive (beta) <a href="#pipedrive" id="pipedrive"></a>

### Preparation <a href="#pipedrive-preparation" id="pipedrive-preparation"></a>

Ask your integration administrator for the OAuth application configured for this MCP connection. If a new registration is needed, use Pipedrive Developer Hub → Create an app and select the appropriate private or public distribution type. Set the app name and Callback URL in Basic info. Use `https://app.artific.nl/oauth/callback`, or the callback on your Artific domain. Save and obtain the Client ID and secret under OAuth & access scopes.

Configure the intended rights and make the app installable for the correct Pipedrive company, including the applicable live or distribution steps. Have the integration administrator confirm that this app can be used with the MCP service. Credentials from a Claude or ChatGPT connection are not reusable Artific app credentials.

### Settings <a href="#pipedrive-settings" id="pipedrive-settings"></a>

| Field                      | Value                                         |
| -------------------------- | --------------------------------------------- |
| Server URL                 | `https://mcp.pipedrive.ai/mcp`                |
| Transport                  | **Streamable HTTP (recommended)**             |
| Authentication             | **OAuth — Per-user**                          |
| Auto-discover (MCP-native) | Off                                           |
| Authorization endpoint     | `https://oauth.pipedrive.com/oauth/authorize` |
| Token endpoint             | `https://oauth.pipedrive.com/oauth/token`     |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#pipedrive-scopes" id="pipedrive-scopes"></a>

Enter the following space-separated scopes, matching the application setup:

```
activities:full admin contacts:full deals:full leads:full search:read
```

### Access and usage <a href="#pipedrive-access-and-usage" id="pipedrive-access-and-usage"></a>

The definition requests `activities:full admin contacts:full deals:full leads:full search:read`, including writing and administration access. Have the integration administrator align scopes with the intended functions and app registration. A reading-only first check does not reduce the granted OAuth rights. Do not put a Pipedrive API token in the Client ID or secret fields.

### Check <a href="#pipedrive-check" id="pipedrive-check"></a>

“Read one existing Pipedrive deal and return its title and stage. Do not change the deal.”

### Troubleshooting <a href="#pipedrive-troubleshooting" id="pipedrive-troubleshooting"></a>

| Problem                                | What to check                                                                  |
| -------------------------------------- | ------------------------------------------------------------------------------ |
| invalid\_client                        | Check the credentials of the same available application.                       |
| The app is unavailable to this company | Review app distribution and company availability.                              |
| OAuth succeeds but MCP rejects access  | Have the integration administrator confirm MCP access for the app and account. |

### Further information <a href="#pipedrive-further-information" id="pipedrive-further-information"></a>

* [Official documentation 1](https://www.pipedrive.com/en/features/mcp-server)
* [Official documentation 2](https://pipedrive.readme.io/docs/client-id-and-client-secret)
* [Official documentation 3](https://pipedrive.readme.io/docs/marketplace-registering-a-private-app)

[Back to the connector index](#connector-index)

## Plaud <a href="#plaud" id="plaud"></a>

### Preparation <a href="#plaud-preparation" id="plaud-preparation"></a>

Use an active Plaud account with Plaud Cloud Sync enabled. Wait for a recording to upload and for its transcript and summary to finish processing. If authorization requires a linked recorder, complete that step in Plaud first. No local installer or API key is needed for this Artific OAuth entry.

### Settings <a href="#plaud-settings" id="plaud-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.plaud.ai/mcp`        |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Check <a href="#plaud-check" id="plaud-check"></a>

“List the titles of my latest Plaud recordings without retrieving full transcripts.”

### Troubleshooting <a href="#plaud-troubleshooting" id="plaud-troubleshooting"></a>

| Problem                        | What to check                                                                                        |
| ------------------------------ | ---------------------------------------------------------------------------------------------------- |
| A new recording is missing     | Check Cloud Sync, upload and transcription processing.                                               |
| Plaud asks for a linked device | Pair the recorder with the same Plaud account before connecting again.                               |
| Team recordings are missing    | Check which files the connected account can access; team membership does not expose every recording. |

### Further information <a href="#plaud-further-information" id="plaud-further-information"></a>

* [Official documentation](https://support.plaud.ai/hc/en-us/articles/57751078986265-Plaud-MCP)

[Back to the connector index](#connector-index)

## Pocket <a href="#pocket" id="pocket"></a>

### Preparation <a href="#pocket-preparation" id="pocket-preparation"></a>

Use the Pocket account associated with heypocketai.com and check that recordings are synchronized and processed. This is the voice-recorder product. The OAuth entry does not need a separate API key. Organization actions require an active membership in the relevant Pocket organization.

### Settings <a href="#pocket-settings" id="pocket-settings"></a>

| Field                      | Value                                |
| -------------------------- | ------------------------------------ |
| Server URL                 | `https://public.heypocketai.com/mcp` |
| Transport                  | **Streamable HTTP (recommended)**    |
| Authentication             | **OAuth — Per-user**                 |
| Auto-discover (MCP-native) | On                                   |

### Check <a href="#pocket-check" id="pocket-check"></a>

“List the titles and dates of my latest Pocket conversations. Do not update action items.”

### Troubleshooting <a href="#pocket-troubleshooting" id="pocket-troubleshooting"></a>

| Problem                                 | What to check                                                     |
| --------------------------------------- | ----------------------------------------------------------------- |
| Recordings are missing                  | Check the account, synchronization and processing in Pocket.      |
| An action requires organization context | Check the connected user’s active Pocket organization membership. |

### Further information <a href="#pocket-further-information" id="pocket-further-information"></a>

* [Official documentation 1](https://docs.heypocketai.com/docs/mcp)
* [Official documentation 2](https://docs.heypocketai.com/docs/api/organization/mcp)

[Back to the connector index](#connector-index)

## PostHog <a href="#posthog" id="posthog"></a>

### What you need <a href="#posthog-requirements" id="posthog-requirements"></a>

A PostHog account with access to the intended project. Some AI-powered actions need additional enablement and can incur usage charges.

### Prepare the service <a href="#posthog-setup" id="posthog-setup"></a>

Sign in through OAuth with your own PostHog account and select the intended project when prompted. The remote connection does not require a pasted personal API key. Ask your organization administrator to allow only required actions. Before using AI-powered actions, check availability and applicable usage charges.

### Settings <a href="#posthog-settings" id="posthog-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.posthog.com/mcp` |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#posthog-check" id="posthog-check"></a>

Ask the assistant: “Show the names of up to three existing dashboards in my PostHog project. Do not change feature flags, experiments, or dashboards.”

### Troubleshooting <a href="#posthog-troubleshooting" id="posthog-troubleshooting"></a>

| Problem                             | What to check                                                               |
| ----------------------------------- | --------------------------------------------------------------------------- |
| Data comes from the wrong project   | Check the signed-in account and project context.                            |
| An AI-powered action is unavailable | Check AI feature enablement and project permissions with the administrator. |

### More information <a href="#posthog-sources" id="posthog-sources"></a>

* [PostHog — setup](https://posthog.com/docs/model-context-protocol)

[Back to connector overview](#connector-index)

## Remote <a href="#remote" id="remote"></a>

### What you need <a href="#remote-requirements" id="remote-requirements"></a>

A Remote employer or employee account. Your role must permit access to the information you intend to use.

### Prepare the service <a href="#remote-setup" id="remote-setup"></a>

Sign in with your own Remote account. No API key, custom OAuth app, or manual scopes are required. If you have multiple Remote profiles, deliberately choose the employer or employee profile. Available tools follow that role. Leave requests submitted through the connector still follow Remote’s normal approval process.

### Settings <a href="#remote-settings" id="remote-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://mcp.remote.com/mcp`  |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#remote-check" id="remote-check"></a>

Ask the assistant: “Read my own available Remote leave balance. Do not submit a request or change personal details.”

### Troubleshooting <a href="#remote-troubleshooting" id="remote-troubleshooting"></a>

| Problem                              | What to check                                                                                                      |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| Employer information is missing      | Check that you selected the correct employer profile with appropriate permissions.                                 |
| Only personal information is visible | That may be correct for an employee profile; reconnect with another profile only when that is the intended access. |

### More information <a href="#remote-sources" id="remote-sources"></a>

* [Remote — setup](https://developer.remote.com/docs/introduction-to-remote-mcp)
* [Remote — reference](https://developer.remote.com/docs/quick-start-guide-2)

[Back to connector overview](#connector-index)

## Sentry <a href="#sentry" id="sentry"></a>

### Preparation <a href="#sentry-preparation" id="sentry-preparation"></a>

Use a Sentry account that can open the intended organization and projects. No API token or local application is needed for this automatic OAuth entry. Select the intended account during authorization.

### Settings <a href="#sentry-settings" id="sentry-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.sentry.dev/mcp`      |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#sentry-access-and-usage" id="sentry-access-and-usage"></a>

You can scope the connection before saving with `https://mcp.sentry.dev/mcp/<organization-slug>/<project-slug>`. Replace both slugs with your project’s values and keep automatic discovery enabled.

### Check <a href="#sentry-check" id="sentry-check"></a>

“Read one recent issue from \[project] and return its title and status. Do not change it.”

### Troubleshooting <a href="#sentry-troubleshooting" id="sentry-troubleshooting"></a>

| Problem                             | What to check                                                     |
| ----------------------------------- | ----------------------------------------------------------------- |
| A project is missing                | Check the Sentry account and project access.                      |
| A scoped endpoint returns no result | Check the organization and project slugs, not just display names. |

### Further information <a href="#sentry-further-information" id="sentry-further-information"></a>

* [Official documentation](https://mcp.sentry.dev/)

[Back to the connector index](#connector-index)

## Simplicate <a href="#simplicate" id="simplicate"></a>

### What you need <a href="#simplicate-requirements" id="simplicate-requirements"></a>

A Simplicate environment and an administrator permitted to create an MCP-enabled API key. This preset uses the officially documented token route.

### Prepare the service <a href="#simplicate-setup" id="simplicate-setup"></a>

1. Ask the administrator to create a key under **Settings → API keys → Add** and enable MCP usage.
2. Replace `https://example.mcp.simplicate.app/mcp` with your own environment’s MCP address. The developer guide uses `https://[environment].mcp.simplicate.app/mcp`; use the exact address confirmed by your administrator.
3. Join **API-key** and **API-secret** with one colon: `[API-key]:[API-secret]`. Enter the complete value in **Bearer token**, without the `Bearer` prefix.
4. This shared token represents the key holder. Review their permissions before sharing the connector.

### Settings <a href="#simplicate-settings" id="simplicate-settings"></a>

| Field          | Value                                    |
| -------------- | ---------------------------------------- |
| Server URL     | `https://example.mcp.simplicate.app/mcp` |
| Transport      | Streamable HTTP (recommended)            |
| Authentication | Bearer token                             |

### Check the connection <a href="#simplicate-check" id="simplicate-check"></a>

Ask the assistant: “Find Simplicate project \[project name] and show its name and status. Do not log time, change sales, or post timeline messages.”

### Troubleshooting <a href="#simplicate-troubleshooting" id="simplicate-troubleshooting"></a>

| Problem                       | What to check                                                                        |
| ----------------------------- | ------------------------------------------------------------------------------------ |
| The key is rejected           | Check the MCP option, environment address, and key:secret combination.               |
| The wrong environment is used | Replace the example address before testing and use a key from that same environment. |

### More information <a href="#simplicate-sources" id="simplicate-sources"></a>

* [Simplicate — setup](https://developer.simplicate.com/docs/mcp/getting_started/)
* [Simplicate — reference](https://developer.simplicate.com/docs/mcp/tools/)

[Back to connector overview](#connector-index)

## Slack <a href="#slack" id="slack"></a>

### Preparation <a href="#slack-preparation" id="slack-preparation"></a>

#### Create and configure the Slack application <a href="#slack-create-and-configure-the-slack-application" id="slack-create-and-configure-the-slack-application"></a>

Open Slack’s app management page and choose Create New App → From scratch in the intended workspace. Slack allows MCP access for internal applications and published directory applications.

Under OAuth & Permissions → Redirect URLs, add `https://app.artific.nl/oauth/callback`, or the callback on your Artific domain. Click Add and then Save URLs.

#### Choose user token scopes <a href="#slack-choose-user-token-scopes" id="slack-choose-user-token-scopes"></a>

Add permissions under User Token Scopes, not Bot Token Scopes. Use `channels:read channels:history` for public channel discovery and reading. Add `search:read.public users:read` for public search and user information, and `chat:write` for posting. Private channels need the relevant `groups:read`, `groups:history` and, for search, `search:read.private` permissions. The user must already have access to those channels. Match these scopes in Artific and reinstall the Slack app when Slack requires it.

#### Enable token rotation and MCP access <a href="#slack-enable-token-rotation-and-mcp-access" id="slack-enable-token-rotation-and-mcp-access"></a>

Under OAuth & Permissions → Advanced token security via token rotation, choose Opt in. This allows refresh tokens; Slack does not let you undo this setting. Existing users must reconnect.

Under Features → Agents → Slack Model Context Protocol (MCP) Server, enable MCP-server access. Agent experience is for an agent inside Slack and is not required. The separate MCP Servers menu is for registering external servers with Slack.

Under Settings → Basic Information → App Credentials, copy Client ID and Client Secret. Signing Secret and Verification Token are different values and cannot replace them.

### Settings <a href="#slack-settings" id="slack-settings"></a>

| Field                      | Value                                        |
| -------------------------- | -------------------------------------------- |
| Server URL                 | `https://mcp.slack.com/mcp`                  |
| Transport                  | **Streamable HTTP (recommended)**            |
| Authentication             | **OAuth — Per-user**                         |
| Auto-discover (MCP-native) | Off                                          |
| Authorization endpoint     | `https://slack.com/oauth/v2_user/authorize`  |
| Token endpoint             | `https://slack.com/api/oauth.v2.user.access` |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#slack-scopes" id="slack-scopes"></a>

Enter the following space-separated scopes, matching the application setup:

```
channels:read channels:history
```

### Access and usage <a href="#slack-access-and-usage" id="slack-access-and-usage"></a>

Although Artific labels the secret optional, this Slack application needs its client secret. The preset scopes are only `channels:read channels:history`. For public search, user information and posting, a matching example is `channels:read channels:history users:read search:read.public chat:write`. Add the same scopes in Slack and Artific. Connect and refresh from the assistant, not by testing a per-user connection at organization scope.

### Check <a href="#slack-check" id="slack-check"></a>

“Read the last five messages in \[channel] and summarize them. Do not post a message.”

### Troubleshooting <a href="#slack-troubleshooting" id="slack-troubleshooting"></a>

| Problem                                        | What to check                                                      |
| ---------------------------------------------- | ------------------------------------------------------------------ |
| redirect\_uri mismatch                         | Check the exact callback and remember Save URLs.                   |
| App is not enabled for Slack MCP server access | Enable the app’s Slack MCP-server access.                          |
| Users must reconnect about every hour          | Check token rotation, then reconnect.                              |
| Reading works but searching or posting fails   | Align User Token Scopes in both Slack and Artific, then reconnect. |

### Further information <a href="#slack-further-information" id="slack-further-information"></a>

* [Official documentation 1](https://docs.slack.dev/ai/slack-mcp-server)
* [Official documentation 2](https://docs.slack.dev/ai/slack-mcp-server/developing/)

[Back to the connector index](#connector-index)

## Smartsheet <a href="#smartsheet" id="smartsheet"></a>

### What you need <a href="#smartsheet-requirements" id="smartsheet-requirements"></a>

A Smartsheet account on Business, Enterprise, or Advanced Work Management, and a valid API access token.

### Prepare the service <a href="#smartsheet-setup" id="smartsheet-setup"></a>

Generate an access token under **Account → Personal Settings → API Access** in Smartsheet, or involve your administrator if policy requires it. Store the token and enter its value in **Bearer token**. Ask your administrator which MCP address matches the account; alternatives are `https://mcp.smartsheet.eu` and `https://mcp.smartsheet.au`. This preset uses token authentication and shares the token holder’s permissions.

### Settings <a href="#smartsheet-settings" id="smartsheet-settings"></a>

| Field          | Value                         |
| -------------- | ----------------------------- |
| Server URL     | `https://mcp.smartsheet.com`  |
| Transport      | Streamable HTTP (recommended) |
| Authentication | Bearer token                  |

### Check the connection <a href="#smartsheet-check" id="smartsheet-check"></a>

Ask the assistant: “Read only the title and column names of Smartsheet sheet \[sheet name or ID]. Do not edit rows or share the sheet.”

### Troubleshooting <a href="#smartsheet-troubleshooting" id="smartsheet-troubleshooting"></a>

| Problem               | What to check                                                  |
| --------------------- | -------------------------------------------------------------- |
| The token is rejected | Check the token, server address, and API-access policy.        |
| A sheet is missing    | Check whether the token holder can access that sheet directly. |

### More information <a href="#smartsheet-sources" id="smartsheet-sources"></a>

* [Smartsheet — setup](https://developers.smartsheet.com/ai-mcp/smartsheet/install-the-smartsheet-mcp-server)
* [Smartsheet — reference](https://developers.smartsheet.com/ai-mcp/smartsheet/install-the-smartsheet-mcp-server/connect-codex)

[Back to connector overview](#connector-index)

## Stripe <a href="#stripe" id="stripe"></a>

### Preparation <a href="#stripe-preparation" id="stripe-preparation"></a>

Select the intended Stripe account and environment, sandbox or live. In Dashboard → API keys, create an agent API key and check its Agent badge. Grant only the required permissions, such as reading customers or subscriptions. Store the key securely. Do not use a publishable key or webhook signing secret.

### Settings <a href="#stripe-settings" id="stripe-settings"></a>

| Field                  | Value                             |
| ---------------------- | --------------------------------- |
| Server URL             | `https://mcp.stripe.com`          |
| Transport              | **Streamable HTTP (recommended)** |
| Authentication         | **Bearer token**                  |
| Auth header (optional) | Leave empty                       |

### Access and usage <a href="#stripe-access-and-usage" id="stripe-access-and-usage"></a>

Use an agent API key now: Stripe has announced that, starting in December 2026, MCP will reject full-access secret keys and restricted keys without an Agent tag. The current Marketplace entry uses a shared bearer key rather than each user’s OAuth account. The key determines the account, environment and rights.

### Check <a href="#stripe-check" id="stripe-check"></a>

“List up to three customers from the connected Stripe environment. Do not create a payment, refund or subscription.”

### Troubleshooting <a href="#stripe-troubleshooting" id="stripe-troubleshooting"></a>

| Problem                  | What to check                                               |
| ------------------------ | ----------------------------------------------------------- |
| Expected data is missing | Check the Stripe account and sandbox versus live mode.      |
| 401                      | Check that the key is valid and marked as an agent API key. |
| An operation is denied   | Review key permissions and allowed actions.                 |

### Further information <a href="#stripe-further-information" id="stripe-further-information"></a>

* [Official documentation 1](https://docs.stripe.com/mcp)
* [Official documentation 2](https://docs.stripe.com/keys)

[Back to the connector index](#connector-index)

## Supabase <a href="#supabase" id="supabase"></a>

### Preparation <a href="#supabase-preparation" id="supabase-preparation"></a>

Use a Supabase account with access to the intended project. Find the project reference in the project settings if you want to restrict the connection. This hosted OAuth entry does not need a database password or service-role key.

### Settings <a href="#supabase-settings" id="supabase-settings"></a>

| Field                      | Value                             |
| -------------------------- | --------------------------------- |
| Server URL                 | `https://mcp.supabase.com/mcp`    |
| Transport                  | **Streamable HTTP (recommended)** |
| Authentication             | **OAuth — Per-user**              |
| Auto-discover (MCP-native) | On                                |

### Access and usage <a href="#supabase-access-and-usage" id="supabase-access-and-usage"></a>

To scope the connection to one project and reading-only queries, change Server URL before saving to `https://mcp.supabase.com/mcp?project_ref=<project-ref>&read_only=true`. Replace the reference with the real project reference. The read\_only setting executes database queries as a reading-only user; also choose the actions the assistant needs.

### Check <a href="#supabase-check" id="supabase-check"></a>

“Show the connected project name and available table names. Do not read table contents or make changes.”

### Troubleshooting <a href="#supabase-troubleshooting" id="supabase-troubleshooting"></a>

| Problem                  | What to check                                                           |
| ------------------------ | ----------------------------------------------------------------------- |
| Several projects appear  | The default endpoint is not project-scoped. Add project\_ref if needed. |
| Writing is denied        | Check whether read\_only=true is intentional.                           |
| A project is unavailable | Check the account, organization role and project reference.             |

### Further information <a href="#supabase-further-information" id="supabase-further-information"></a>

* [Official documentation](https://supabase.com/docs/guides/ai-tools/mcp)

[Back to the connector index](#connector-index)

## Tally <a href="#tally" id="tally"></a>

### What you need <a href="#tally-requirements" id="tally-requirements"></a>

A Tally account with access to the required workspaces and forms. The vendor describes this MCP functionality as beta.

### Prepare the service <a href="#tally-setup" id="tally-setup"></a>

Sign in with the Tally account containing your forms and review the requested access. This preset uses OAuth with automatic registration; no API key needs to be pasted. Agree which forms the assistant may edit. New forms begin as drafts, but some settings on existing forms can take effect immediately.

### Settings <a href="#tally-settings" id="tally-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://api.tally.so/mcp`    |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#tally-check" id="tally-check"></a>

Ask the assistant: “Show the names and publication status of up to three Tally forms. Do not read submissions, change anything, or publish.”

### Troubleshooting <a href="#tally-troubleshooting" id="tally-troubleshooting"></a>

| Problem                         | What to check                                                                 |
| ------------------------------- | ----------------------------------------------------------------------------- |
| A form is missing               | Check the account and workspace access.                                       |
| A change is immediately visible | Some settings apply immediately. Use read actions only for the initial check. |

### More information <a href="#tally-sources" id="tally-sources"></a>

* [Tally — setup](https://tally.so/help/mcp)
* [Tally — reference](https://developers.tally.so/api-reference/mcp)

[Back to connector overview](#connector-index)

## Teamleader Orbit <a href="#teamleader-orbit" id="teamleader-orbit"></a>

### Preparation <a href="#teamleader-orbit-preparation" id="teamleader-orbit-preparation"></a>

Use an Orbit account, not a Teamleader Focus account. Have the administrator grant MCP read to your role. Add MCP write only for intended changes. Refresh Orbit after changing the role. No shared API key or separately registered OAuth application is needed.

### Settings <a href="#teamleader-orbit-settings" id="teamleader-orbit-settings"></a>

| Field                      | Value                                 |
| -------------------------- | ------------------------------------- |
| Server URL                 | `https://api.orbit.teamleader.eu/mcp` |
| Transport                  | **Streamable HTTP (recommended)**     |
| Authentication             | **OAuth — Per-user**                  |
| Auto-discover (MCP-native) | On                                    |

### Access and usage <a href="#teamleader-orbit-access-and-usage" id="teamleader-orbit-access-and-usage"></a>

Orbit keeps your existing account permissions. Start with a reading action. Orbit writing permissions and Artific’s allowed actions are separate settings.

### Check <a href="#teamleader-orbit-check" id="teamleader-orbit-check"></a>

“Read one existing Orbit project and show its name and status. Do not book time or create an invoice.”

### Troubleshooting <a href="#teamleader-orbit-troubleshooting" id="teamleader-orbit-troubleshooting"></a>

| Problem                         | What to check                                 |
| ------------------------------- | --------------------------------------------- |
| MCP access is denied            | Check MCP read on the role and refresh Orbit. |
| Reading works but writing fails | Check MCP write and allowed actions.          |
| You have Teamleader Focus       | This endpoint requires Orbit.                 |

### Further information <a href="#teamleader-orbit-further-information" id="teamleader-orbit-further-information"></a>

* [Official documentation](https://www.teamleader.eu/blog/teamleader-orbit-mcp)

[Back to the connector index](#connector-index)

## Todoist <a href="#todoist" id="todoist"></a>

### What you need <a href="#todoist-requirements" id="todoist-requirements"></a>

A Todoist account with access to the required projects. Specific features may depend on your plan and project permissions.

### Prepare the service <a href="#todoist-setup" id="todoist-setup"></a>

This OAuth route requires no custom app registration or API token. Sign in with the Todoist account managing the tasks and review consent. Check that account’s permissions in shared projects. Ask your organization administrator to decide whether the assistant may complete, move, or delete tasks.

### Settings <a href="#todoist-settings" id="todoist-settings"></a>

| Field                      | Value                         |
| -------------------------- | ----------------------------- |
| Server URL                 | `https://ai.todoist.net/mcp`  |
| Transport                  | Streamable HTTP (recommended) |
| Authentication             | OAuth — Per-user              |
| Auto-discover (MCP-native) | On                            |

### Check the connection <a href="#todoist-check" id="todoist-check"></a>

Ask the assistant: “Show titles and due dates for up to three existing Todoist tasks. Do not complete anything or change the schedule.”

### Troubleshooting <a href="#todoist-troubleshooting" id="todoist-troubleshooting"></a>

| Problem                     | What to check                                                                  |
| --------------------------- | ------------------------------------------------------------------------------ |
| A shared project is missing | Check whether the same Todoist account belongs to that project.                |
| A task action is refused    | Check project permissions, available features, and allowed actions in Artific. |

### More information <a href="#todoist-sources" id="todoist-sources"></a>

* [Todoist — setup](https://developer.todoist.com/)

[Back to connector overview](#connector-index)

## Typeform <a href="#typeform" id="typeform"></a>

### What you need <a href="#typeform-requirements" id="typeform-requirements"></a>

A Typeform account with access to the required forms and workspaces.

### Prepare the service <a href="#typeform-setup" id="typeform-setup"></a>

Sign in through OAuth with your Typeform account. Personal access tokens are not supported for this MCP route. If your account uses a different address, ask your administrator which endpoint is required; the official guide also lists `https://api.eu.typeform.com/mcp` and `https://api.typeform.eu/mcp`. Change the address before connecting and review the requested access.

### Settings <a href="#typeform-settings" id="typeform-settings"></a>

| Field                      | Value                          |
| -------------------------- | ------------------------------ |
| Server URL                 | `https://api.typeform.com/mcp` |
| Transport                  | Streamable HTTP (recommended)  |
| Authentication             | OAuth — Per-user               |
| Auto-discover (MCP-native) | On                             |

### Check the connection <a href="#typeform-check" id="typeform-check"></a>

Ask the assistant: “Show the titles of up to three Typeform forms I can open. Do not retrieve responses or change anything.”

### Troubleshooting <a href="#typeform-troubleshooting" id="typeform-troubleshooting"></a>

| Problem                            | What to check                                                                       |
| ---------------------------------- | ----------------------------------------------------------------------------------- |
| Sign-in does not work with a token | Use OAuth; a personal access token does not replace that flow.                      |
| Forms or actions are missing       | Check the account, endpoint, and workspace permissions, then refresh the connector. |

### More information <a href="#typeform-sources" id="typeform-sources"></a>

* [Typeform — setup](https://help.typeform.com/hc/en-us/articles/47604941255700-Use-Typeform-from-Claude)

[Back to connector overview](#connector-index)

## Wrike <a href="#wrike" id="wrike"></a>

### What you need <a href="#wrike-requirements" id="wrike-requirements"></a>

A Wrike account and an administrator with access to **Apps & Integrations** to configure an OAuth app.

### Prepare the service <a href="#wrike-setup" id="wrike-setup"></a>

1. In Wrike, open your profile menu → **Apps & Integrations → API → Create new app** and choose a recognizable name.
2. Store the **OAuth Client ID** and **Secret key** and enter them in the designated Artific fields.
3. Register `https://app.artific.nl/oauth/callback` under **Redirect URLs**, or the same route on your Artific domain, and save.
4. Disable **Auto-discover**. Use the v2 server address and prefilled OAuth endpoints and scope.
5. Each user signs in with their own Wrike account. Registering the app grants no additional project access.

### Settings <a href="#wrike-settings" id="wrike-settings"></a>

| Field                      | Value                                         |
| -------------------------- | --------------------------------------------- |
| Server URL                 | `https://mcp.wrike.com/v2`                    |
| Transport                  | Streamable HTTP (recommended)                 |
| Authentication             | OAuth — Per-user                              |
| Auto-discover (MCP-native) | Off                                           |
| Authorization endpoint     | `https://login.wrike.com/oauth2/authorize/v4` |
| Token endpoint             | `https://login.wrike.com/oauth2/token`        |
| Scopes                     | `wsReadWrite`                                 |

### Check the connection <a href="#wrike-check" id="wrike-check"></a>

Ask the assistant: “Show the title and status of up to three Wrike tasks assigned to me. Do not create or change work items.”

### Troubleshooting <a href="#wrike-troubleshooting" id="wrike-troubleshooting"></a>

| Problem                                  | What to check                                                                                                        |
| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| OAuth reports a client or callback error | Check the Client ID, Secret key, and exact Redirect URL of the same app.                                             |
| The wrong tools appear                   | Use `https://mcp.wrike.com/v2`; the older `/app/mcp/stream` and `/app/mcp/sse` addresses expose a different toolset. |

### More information <a href="#wrike-sources" id="wrike-sources"></a>

* [Wrike — setup](https://developers.wrike.com/docs/connect-wrike-mcp-as-a-custom-connector)
* [Wrike — reference](https://developers.wrike.com/docs/oauth-20-authorization)

[Back to connector overview](#connector-index)

## Zoom Meetings <a href="#zoom-meetings" id="zoom-meetings"></a>

### Preparation <a href="#zoom-meetings-preparation" id="zoom-meetings-preparation"></a>

Use existing integration credentials or have a Zoom administrator or developer open Zoom App Marketplace → Develop → Build app → General app. Under Basic information → OAuth Information, register the redirect URL `https://app.artific.nl/oauth/callback`, or the callback on your Artific domain. Copy Client ID and Client Secret from App Credentials.

Under Scopes → Add scopes, add the required Meetings permissions and align them with Artific’s scope list. Have the administrator complete applicable activation or distribution steps for the intended users. Zoom requires manual client registration for this connection.

### Settings <a href="#zoom-meetings-settings" id="zoom-meetings-settings"></a>

| Field                      | Value                                        |
| -------------------------- | -------------------------------------------- |
| Server URL                 | `https://mcp.zoom.us/mcp/meeting/streamable` |
| Transport                  | **Streamable HTTP (recommended)**            |
| Authentication             | **OAuth — Per-user**                         |
| Auto-discover (MCP-native) | Off                                          |
| Authorization endpoint     | `https://zoom.us/oauth/authorize`            |
| Token endpoint             | `https://zoom.us/oauth/token`                |

Use the Client ID and client secret of the application described above. Keep automatic discovery off.

### Scopes <a href="#zoom-meetings-scopes" id="zoom-meetings-scopes"></a>

Enter the following space-separated scopes, matching the application setup:

```
meeting:write:meeting meeting:read:search meeting:delete:meeting meeting:update:in_meeting_controls meeting:update:meeting meeting:read:assets cloud_recording:read:list_user_recordings cloud_recording:read:content
```

### Access and usage <a href="#zoom-meetings-access-and-usage" id="zoom-meetings-access-and-usage"></a>

For reading-only usage, retain meeting:read:search, meeting:read:assets, cloud\_recording:read:list\_user\_recordings and cloud\_recording:read:content in both configurations. The full definition also permits creating, changing, deleting and controlling meetings. Available recordings depend on licenses and account access. Zoom’s OAuth flow requires PKCE and client\_secret\_basic; token-exchange failures may need the integration administrator’s help.

### Check <a href="#zoom-meetings-check" id="zoom-meetings-check"></a>

“Find one existing Zoom meeting and show its title and date. Do not create or change meetings.”

### Troubleshooting <a href="#zoom-meetings-troubleshooting" id="zoom-meetings-troubleshooting"></a>

| Problem                      | What to check                                                     |
| ---------------------------- | ----------------------------------------------------------------- |
| Automatic registration fails | Leave automatic discovery off and use the registered General app. |
| OAuth fails                  | Check the app configuration, credentials and redirect URL.        |
| A recording is missing       | Check its availability, license and account access.               |

### Further information <a href="#zoom-meetings-further-information" id="zoom-meetings-further-information"></a>

* [Official documentation 1](https://developers.zoom.us/docs/mcp/servers/connect-to-zoom-mcp-servers/)
* [Official documentation 2](https://developers.zoom.us/docs/mcp/zoom-meetings-mcp-server/)

[Back to the connector index](#connector-index)
