---
title: "INTEGRATIONS - Claude: connect to Qargo over MCP - Walkthrough"
description: "Connect a Qargo account to Claude, then ask Claude questions about live data. Who sets it up depends on the Claude plan, and Claude Code follows a different route."
url: https://help.qargo.com/us/articles/799799-integrations-claude-connect-to-qargo-over-mcp-walkthrough
locale: us
updated: 2026-11-10
---

# INTEGRATIONS - Claude: connect to Qargo over MCP - Walkthrough

## Prerequisites {#h_93d72c977a}

-   **Qargo Intelligence on the tenant.** MCP is part of the Qargo Intelligence add-on. If the tenant does not have it, contact the Account Manager.
-   **MCP access set for the user.** A Super admin in the organization sets it in **Configuration > Organization settings > Users**. No request to Qargo is needed. See [INTEGRATIONS - Connect an AI assistant to Qargo over MCP](https://help.qargo.com/us/articles/799560-integrations-connect-an-ai-assistant-to-qargo-over-mcp-walkthrough) for the steps.
-   **The usual Qargo sign-in details.** There is no separate key or token.

| **Setup** | **Who adds the Qargo connector** | **Sections to follow** |
| --- | --- | --- |
| Claude Desktop or [claude.ai](http://claude.ai), Team or Enterprise | An Owner, once for the organization | _Team and Enterprise: add the connector_, then _Team and Enterprise: connect an account_ |
| Claude Desktop or [claude.ai](http://claude.ai), Free, Pro or Max | Each user, individually | _Free, Pro and Max: add the connector individually_ |
| Claude Code | Each user, per project | _Claude Code: register the server_ |

:::callout{tone="note"}
**📚 Use [https://mcp.qargo.com/mcp](https://mcp.qargo.com/mcp).** The Qargo API documentation site offers **Connect to Cursor** and **Connect to VS Code** buttons that point to a different server. That server reads the API reference only and cannot see tenant data.
:::

## Team and Enterprise: add the connector {#h_fe2a9cc000}

On Team and Enterprise plans, only an Owner can add a custom connector. Add it once for the whole organization. Members then connect their own Qargo accounts.

### Requirements {#h_6bcb4ec067}

-   **Owner or Primary Owner rights** in the Claude organization. Members cannot add custom connectors.
-   **MCP access set in Qargo** for the users who need it. A Super admin sets it per user in **Configuration > Organization settings > Users**. Do this before adding the connector, so members can connect immediately.

### Add the connector {#h_c295db9f8c}

1.  Navigate to **Organization settings > Connectors**.
2.  Click **Add**, then **Custom**. Choose **Web** if Claude asks for a connector type.
3.  Enter Qargo as the name.
4.  Enter [https://mcp.qargo.com/mcp](https://mcp.qargo.com/mcp) as the remote MCP server URL.
5.  Click **Continue**.
6.  Leave **Authentication** and **OAuth client** as Claude fills them in. Claude detects the correct settings for Qargo, so there is no need to open **Advanced** or enter an OAuth client ID or secret.
7.  Click **Add**.

### What adding it does, and does not do {#h_c5962109a9}

-   **Adding the connector grants nobody access to data.** It only makes Qargo available to connect to.
-   **Each member authenticates separately** and receives only their own Qargo permissions.
-   **Claude settings cannot widen Qargo access.** A member on **Read-only** cannot change data, whatever the organization allows. Levels are set per user in Qargo, under **Configuration > Organization settings > Users**.

Members then follow the next section.

* * *

## Team and Enterprise: connect an account {#h_ed8c302ab1}

Qargo should already appear in the connector list. If it does not, ask an Owner to add it.

1.  Navigate to **Customize > Connectors**.
2.  Find Qargo in the list and click **Connect**.
3.  Sign in with the normal Qargo credentials when the browser opens.
4.  Approve the access request. The browser returns to Claude.

![](https://help.qargo.com/media/ad8398c1eb6d-Screenshot-2026-08-24-at-10_07_43.png)

* * *

## Free, Pro and Max: add the connector individually {#h_70781fbbbf}

On an individual plan, there is no Owner to wait for. The Free plan allows one custom connector.

1.  Navigate to **Customize > Connectors**.
2.  Click **Add** at the top right of the **Connectors** panel, then **Add custom connector**.
3.  Enter Qargo as the name and [https://mcp.qargo.com/mcp](https://mcp.qargo.com/mcp) as the remote MCP server URL.
4.  Click **Continue**.
5.  Leave **Authentication** and **OAuth client** as Claude fills them in. Claude detects the correct settings for Qargo, so there is no need to open **Advanced** or enter an OAuth client ID or secret.
6.  Click **Add**, then **Connect**, and sign in with the Qargo credentials.

![](https://help.qargo.com/media/08ad8b2e1a72-Screenshot-2026-08-24-at-10_06_58.png)

* * *

## Claude Code: register the server {#h_9a1a9db10e}

Claude Code uses one terminal command instead of a settings panel. Every user sets this up individually, whatever the plan.

:::callout{tone="note"}
📚 **This might not be needed at all.** A connector already added on [claude.ai](http://claude.ai) loads automatically in Claude Code when the user signs in with the same account. Follow the steps below only if Qargo does not appear.
:::

### Requirements {#h_e8031904df}

-   **Claude Code installed** and working in the project that needs Qargo access.
-   **A local browser.** Authentication opens one. It cannot be completed over a remote shell session.

### Register the server {#h_bf6ae0c6cb}

1.  Open a terminal in the project that should have access.
2.  Run claude mcp add --transport http qargo [https://mcp.qargo.com/mcp](https://mcp.qargo.com/mcp).
3.  Run claude mcp list. Qargo shows as **Needs authentication**, which is expected at this point.
4.  Type /mcp inside Claude Code.
5.  Select qargo, press Enter, then choose **Authenticate**. A browser window opens.
6.  Sign in with the normal Qargo credentials. The terminal then reports the server as authenticated.

:::callout{tone="info"}
📚 **Scope matters.** Registering inside a project limits the server to that project. Add --scope user only if every project should reach the user's Qargo data.
:::

* * *

## Verify the connection {#h_afd8ac38a9}

Ask Claude to list the Qargo tenants. A reply naming the tenant confirms that the connection works.\
Name Qargo in the question when Claude answers from general knowledge instead of Qargo data, for example: _ask Qargo which orders are still unplanned for tomorrow_.

:::callout{tone="info"}
📚**Each user gets their own permissions.** Claude sees exactly what the user can see in Qargo. A colleague with wider access sees more through the same connector.
:::

* * *

## Changing data {#h_edbe5b6b04}

The first change to production data in a session is stopped, and Claude returns an approval link. Open it, approve, and ask Claude to retry. Full steps are in [INTEGRATIONS - Connect an AI assistant to Qargo over MCP](https://help.qargo.com/us/articles/799560-integrations-connect-an-ai-assistant-to-qargo-over-mcp-walkthrough).

:::callout{tone="warning"}
‼️ **Check what is being approved.** Approving a session authorizes every further change in it, not only the one requested. Review anything that affects more than one record.
:::

* * *

## Troubleshooting {#h_5a072e2b75}

| **Issue** | **Resolution** |
| --- | --- |
| Qargo is not in the connector list and the **Add** menu offers no **Add custom connector** option | The account is on Team or Enterprise. Ask an Owner to add the connector. |
| The **Add** button is missing from **Organization settings** | The user is not an Owner or Primary Owner. Ask one to add the connector. |
| Members cannot see Qargo in their connector list | Confirm that the connector was added at the organization level, not in a personal profile. |
| The browser shows an unknown client error during sign-in | Reconnect the connector. On Team or Enterprise, ask an Owner to remove and re-add it. This can happen after a Qargo platform update. |
| The connector is listed but Claude has no Qargo tools | Either the session expired (sessions typically last a day), so connect again, or Qargo is switched off for this conversation. Click the **+** button in the chat, hover over **Connectors**, and toggle Qargo on. |
| Claude reports that MCP access is not enabled for the user | The user's access is still set to **Disabled**. Ask a Super admin to set it in **Configuration > Organization settings > Users**. |
| Claude can list tenants but every other request fails | External API access is not enabled on the tenant. Contact the Account Manager. |
| A read works but a change is refused | The user is on **Read-only**. A Super admin can change the level in **Configuration > Organization settings > Users**. |
| No browser opens during Claude Code authentication | The session is running over a remote shell. Authenticate on a machine with a browser instead. |
| /mcp does not list qargo | The current project is different from the one where the server was registered. Change directory, or add the server again with --scope user. |
| The terminal reports an unknown client error | Remove the server with claude mcp remove qargo, then add it again. This can happen after a Qargo platform update. |


## Related articles

- [Integrations – ChatGPT: connect to Qargo over MCP – walkthrough](https://help.qargo.com/us/articles/800127-integrations-chatgpt-connect-to-qargo-over-mcp-walkthrough.md)
- [Integrations – Qargo API – What, why & how](https://help.qargo.com/us/articles/865547-integrations-qargo-api-what-why-how.md)
- [Integrations – WhatsApp configuration](https://help.qargo.com/us/articles/355075-integrations-whatsapp-configuration.md)
- [FAQ: Logging in to Qargo](https://help.qargo.com/us/articles/374948-faq-logging-in-to-qargo.md)
- [Intermodal – Customs UK HMRC integration](https://help.qargo.com/us/articles/543446-intermodal-customs-uk-hmrc-integration.md)
