Prerequisites
MCP access set for your user. An administrator in your organisation sets it in Configuration > Organisation settings > Users. See INTEGRATIONS - Connect an AI assistant to Qargo over MCP for the prerequisites.
Your usual Qargo sign-in details. There is no separate key or token.
Your setup | Who adds the Qargo connector | Sections to follow |
Claude Desktop or claude.ai, Team or Enterprise | An Owner, once for the organisation | Team and Enterprise: add the connector, then Team and Enterprise: connect your account |
Claude Desktop or claude.ai, Pro or Max | You, for yourself | Pro and Max: add the connector yourself |
Claude Code | You, per project | Claude Code: register the server |
📚 Use https://mcp.qargo.com/mcp. The Qargo API documentation site offers Connect to Cursor and Connect to VS Code buttons pointing at a different server. That one reads the API reference only and cannot see your data.
Team and Enterprise: add the connector
On Team and Enterprise plans, only an Owner can add a custom connector. Add it once for the whole organisation. Members then connect their own Qargo accounts.
Requirements
Owner or Primary Owner rights in your Claude organisation. Members cannot add custom connectors.
MCP access set in Qargo for the users who need it. A Qargo administrator sets it per user in Configuration > Organisation settings > Users. Do this before you add the connector, so members can connect immediately.
Add the connector
NAVIGATE to Organization settings > Connectors.
CLICK Add.
ENTER Qargo as the name.
ENTER https://mcp.qargo.com/mcp as the remote MCP server URL.
SKIP Advanced settings. Qargo needs no OAuth client ID or secret.
CLICK Add.
What adding it does, and does not do
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 your organisation allows. Levels are set per user in Qargo, under Configuration > Organisation settings > Users.
Tell your members to follow the next section.
Team and Enterprise: connect your account
Qargo should already appear in your connector list. If it does not, ask an Owner to add it.
NAVIGATE to Customize > Connectors.
FIND Qargo in the list and click Connect.
SIGN IN with your normal Qargo credentials when the browser opens.
APPROVE the access request. The browser returns to Claude.
Pro and Max: add the connector yourself
On an individual plan there is no Owner to wait for.
NAVIGATE to Customize > Connectors.
CLICK the + button next to Connectors.
ENTER Qargo as the name and https://mcp.qargo.com/mcp as the URL.
SKIP advanced settings. Qargo needs no OAuth client ID or secret.
CLICK Add, then Connect, and sign in with your Qargo credentials.
Claude Code: register the server
Claude Code uses one terminal command instead of a settings panel. Every user sets this up for themselves, whatever the plan.
Requirements
Claude Code installed and working in the project that needs Qargo access.
A local browser. Authentication opens one. It cannot complete over a remote shell session.
Register the server
OPEN a terminal in the project that should have access.
RUN claude mcp add --transport http qargo https://mcp.qargo.com/mcp.
TYPE /mcp inside Claude Code.
SELECT qargo to start authentication. A browser window opens.
SIGN IN with your normal Qargo credentials. The terminal then reports the server as authenticated.
📚 Scope matters. Registering inside a project limits the server to that project. Use the global scope only if every project should reach your Qargo data.
Verify the connection
Ask Claude to list your Qargo tenants. A reply naming your tenant confirms the connection works.
Name Qargo in your question when Claude answers from general knowledge instead of your data, for example: ask Qargo which orders are still unplanned for tomorrow.
📚You get your own permissions. Claude sees exactly what you can see in Qargo. A colleague with wider access sees more through the same connector.
Changing data
Your 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.
‼️ Check what you approve. Approving a session authorises every further change in it, not only the one requested. Review anything affecting more than one record.
Troubleshooting
Issue | Resolution |
Qargo is not in your connector list and there is no + button | You are on Team or Enterprise. Ask an Owner to add the connector. |
The Add button is missing from Organization settings | You are not an Owner or Primary Owner. Ask one to add the connector. |
Members cannot see Qargo in their connector list | Confirm the connector was added at organisation 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 | Your session expired. Connect again. Sessions typically last a day. |
Claude reports that MCP access is not enabled for your user | Your access is still set to Disabled. Ask an administrator to set it in Configuration > Organisation settings > Users. |
Claude can list tenants but every other request fails | External API access is not enabled on the tenant. Contact your Account Manager. |
A read works but a change is refused | You are on Read-only. An administrator can change your level in Configuration > Organisation settings > Users. |
No browser opens during Claude Code authentication | You are working over a remote shell. Authenticate on a machine with a browser instead. |
/mcp does not list qargo | You are in a different project from the one where you registered it. Change directory, or register the server globally. |
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. |