Every client below talks to the same connector, https://mcp.avrix.io/mcp, and signs you in with
your Avrix account. Pick your client, follow the steps, then say "Call avrix_whoami" to confirm
which company the assistant is bound to.
Claude (web and desktop)#
- Open Settings → Connectors → Add custom connector.
- Enter the name
Avrixand the URLhttps://mcp.avrix.io/mcp, then Add. - Click Connect; your browser opens the Avrix sign-in and consent screen.
- Choose the company and the access you want to grant, then Allow.
Claude Desktop uses the same connector once it is added on the web.
Claude Code#
claude mcp add --transport http avrix https://mcp.avrix.io/mcp
Then run /mcp inside Claude Code, choose avrix and Authenticate. Claude Code opens the
consent screen in your browser and receives the result on a local callback; the consent screen
mentions that an app on your device asked for access.
Cursor#
- Settings → MCP → Add new MCP server.
- Type: Streamable HTTP; URL:
https://mcp.avrix.io/mcp. - Click the connect prompt; Cursor registers itself with Avrix, opens the consent screen and
returns through the
cursor://link.
VS Code (Copilot agent mode)#
Run MCP: Add Server from the command palette, choose HTTP, paste the URL and give it the id
avrix. Start the server from the MCP view; VS Code opens the consent screen.
ChatGPT#
In Settings → Connectors (developer mode), choose Create, enter the name and the connector URL, and select OAuth for authentication. ChatGPT discovers Avrix's sign-in automatically and opens the consent screen when you first use the connector.
Codex CLI#
Add to ~/.codex/config.toml:
[mcp_servers.avrix]
url = "https://mcp.avrix.io/mcp"
Then run codex mcp login avrix to sign in through your browser.
Headless use with an API key#
Automation that cannot open a browser can present a Seller API key (or a short-lived OAuth token minted from one) instead of signing in:
claude mcp add --transport http avrix https://mcp.avrix.io/mcp \
--header "Authorization: Bearer avrix_sk_sandbox_your_key"
The connection is then bound to the key's company and environment, gets Seller API tools only, and follows the key's scopes and IP allowlist. Keys and OAuth tokens are described under Authentication and Seller API OAuth tokens.
Working on several companies#
A connection serves one company. To work on another, add the connector a second time under a
different name (for example Avrix – Sandbox and Avrix – Production) and pick the other company
or environment at sign-in.
Troubleshooting#
| Symptom | What it means | What to do |
|---|---|---|
The connector URL answers 404 Not Found | The connector is not switched on for this environment yet | Ask your Avrix contact; see Availability in the overview |
| The client says authentication is required in a loop | The access token was revoked or the connection was removed | Reconnect; check Profile → Connected apps |
403 insufficient_scope | The tool family needs access you did not grant | Reconnect and tick the missing access |
429 with Retry-After | Per-minute limit or daily quota reached | Wait for the indicated time |
| Seller API tools are missing | You connected a Content Owner company, or did not grant Seller API access | Reconnect with a Content Seller company and grant Seller API access |
| Production is greyed out on the consent screen | The company has not enabled the API model | Enable it under Settings → Distribution models |
| The consent screen shows an app name you do not recognise | The requesting client is identified by its URL or registration | Deny and report it to support |