What an assistant can do
An assistant reaches the same data as the Qargo external API, on behalf of one named user, with that user's own permissions. Read the Qargo API available options FAQ for the full scope: orders, trips, tasks, companies, resources, documents and accounting.
Not available through MCP:
Tenant configuration. Feature flags, integration setup and organisation settings stay out of reach.
An assistant never sees more than the user it acts for. A user without access to financial data in Qargo cannot retrieve it through an assistant either.
Connector address
Use https://mcp.qargo.com/mcp in every assistant.
Step 1: Set MCP access for the user
MCP access is a separate setting per user. It defaults to Disabled for everyone, and a tenant administrator sets it.
NAVIGATE to Configuration > Organisation settings > Users.
CLICK the pencil icon next to the user.
SELECT a level under MCP access.
CLICK Save.
Level | What the assistant can do |
Disabled | Nothing. No MCP tools at all. This is the default. |
Read-only | Every read operation. Anything that creates, updates or deletes is refused. |
Read and write | Reads, plus create, update and delete. |
‼️ Be careful with Read and write. An assistant with write access can change or delete data across your whole tenant, and one wrong bulk update can take hours to unpick. Keep users on Read-only by default. Grant Read and write only to users who understand the consequences.
Step 2: Add the connector in your assistant
You can connect any AI assistant that supports MCP. Quick steps for Claude and ChatGPT are below.
Claude: quick steps
Claude: quick steps
Pro or Max, in Claude Desktop or the web app
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.
Team or Enterprise, in Claude Desktop or the web app
ADD the connector once as an Owner, under Organization settings > Connectors > Add, using the name and URL above.
CONNECT your own account as a member, under Customize > Connectors, then sign in with your Qargo credentials.
Claude Code
RUN claude mcp add --transport http qargo <https://mcp.qargo.com/mcp> in the project that needs access.
TYPE /mcp, select qargo, and sign in when the browser opens.
Full steps and troubleshooting: INTEGRATIONS - Claude: connect to Qargo over MCP.
ChatGPT: quick steps
ChatGPT: quick steps
Plus or Pro
OPEN ChatGPT settings and turn on developer mode.
ADD a custom connector named Qargo, with https://mcp.qargo.com/mcp as the URL.
SELECT OAuth as the authentication method. Leave client ID and secret empty.
SIGN IN with your Qargo credentials and approve the access request.
ENABLE the connector in your conversation.
Business, Enterprise or Education
PUBLISH the app once as a workspace owner: turn on developer mode, create a custom app with the name and endpoint above, select OAuth, scan the tools, test as a draft, publish, then set user access.
CONNECT your own account as a member: open the Qargo app and sign in with your Qargo credentials.
Free plans cannot add custom connectors.
The article for each assistant carries the full setup, the plan requirements and its own troubleshooting.
Assistant | Who sets it up | Article |
Claude Desktop, claude.ai and Claude Code | An Owner on Team and Enterprise, each user on Pro, Max and Claude Code | |
ChatGPT | A workspace owner on Business, Enterprise and Education, each user on Plus and Pro |
📚 Assistants move their settings. Menu paths change between versions and plans. If a path above does not match what you see, search your assistant's settings for connectors or developer mode.
Approve a change to production data
Read requests run immediately. The first time an assistant tries to change data in a production tenant, Qargo stops it and returns an approval link.
OPEN the approval link in a browser where you are already signed in to Qargo.
REVIEW the tenant named on the approval page and check it is the right one.
APPROVE the session.
RETURN to the assistant and ask it to retry the change.
Approval covers that user, that tenant and that assistant session only. A new session needs a new approval.
‼️ Approving a session authorises every further change in it, not only the one requested. Review any change an assistant proposes before approving, especially changes affecting more than one record.
Daily use
Sessions expire. You might have to re-authenticate the connector periodically to stay signed in.
Reporting is not supported. Send requests for totals, averages or dashboards to BigQuery or the external API instead.
Rate limits are shared with your tenant's other API traffic.
📚 AI assistants make mistakes. Check the output before relying on it, and review any proposed change to production data before approving it.
Troubleshooting
Issue | Resolution |
The assistant reports that MCP access is not enabled for the user | That user is still set to Disabled. An administrator sets the level in Configuration > Organisation settings > Users. |
A read works but a change is refused | The user is set to Read-only. An administrator can change the level. |
The assistant reports that access is denied and mentions Qargo Intelligence | The tenant does not have Qargo Intelligence enabled. Contact your Account Manager. |
The assistant can list tenants but every other request fails | External API access is not enabled on the tenant. Contact your Account Manager. |
The assistant asks for approval again in the same conversation | A new session started. Open the new approval link and approve again. |
The assistant stops responding after many requests | The tenant rate limit is reached. Wait for the period stated in the response. |
Setup problems specific to one assistant | See the troubleshooting section in that assistant's setup article. |