The MCP endpoint uses OAuth with PKCE, and it is strict about who connects and what they may do. These are the messages and what each one actually means.
Not an approved connector
This Argorant MCP connection request is not from an approved connector.
The client that started the authorization is not on the approved list. Officially supported clients include Claude and Claude Code, ChatGPT with a custom connector, Codex, Cursor and Grok, plus native app schemes like cursor://. A custom or self-built client should use the REST API with a bearer key instead, which is fully supported and needs no approval.
The request expired
This Argorant MCP connection request has expired. Please try again.
Authorization requests are short-lived. This appears when the browser window sat open while you went to find your password. Close it and start the connect flow again from the client.
The action is not enabled
This Argorant MCP action is not enabled for this account.
This Argorant connector is not allowed to use that action
Tools are mapped to scopes, and spending tools are separate from free ones. If your agent can count and preview but not reveal or export, that is the design working: reconnect and grant the spending scopes, or leave them off deliberately for a read-only agent.
Token problems
Missing MCP bearer token
Invalid MCP bearer token
Invalid or expired grant
Unknown scope(s):
Disconnect the connector in the client and reconnect. A stored token from a revoked key or a deleted account cannot be repaired, only replaced.
Server-side enforcement is the point: rate limits, scopes and credit checks all run on our side, so a misconfigured or misbehaving agent can never spend more than your balance.