The connector uses OAuth 2.1 with PKCE. MCP clients discover Avrix's authorization server automatically, so there is nothing to configure beyond the connector URL. This page explains what happens at each step and how permissions are shaped.
The flow#
- The client calls
https://mcp.avrix.io/mcpwithout credentials and receives a401that points to Avrix's protected-resource metadata (/.well-known/oauth-protected-resource/mcp). - From there it reads the authorization server metadata on
https://app.avrix.ioand identifies itself either with a Client ID Metadata Document (a URL the client hosts) or by dynamic registration. - It opens the consent screen:
https://app.avrix.io/oauth/authorize. You sign in as usual — including two-factor authentication when your account requires it. - You choose the company, the Seller API environment and scopes (for Content Seller companies), and the console tool families, then Allow or Deny.
- The client exchanges the short-lived code for an access token (one hour) and a refresh token, and starts calling tools.
Avrix publishes the standard documents clients expect: client_id_metadata_document_supported,
authorization_response_iss_parameter_supported, PKCE S256 only, authorization_code and
refresh_token grants, token revocation.
What the consent screen shows#
- Who is asking — the client's name and, for hosted clients, the host it is identified by. A warning appears when the client runs on your own device (Claude Code, Codex, Cursor).
- Company — one of your memberships. Platform staff see their own memberships only.
- Seller API (Content Seller companies where you may create API keys) — sandbox or production, plus the individual scopes such as Place orders and pull keys or Report refunds.
- Console access — read-only tool families per area. Make changes on your behalf is a separate, opt-in grant that always asks for your confirmation per change once console tools are available.
- Tool set — Essentials (pre-selected: the identity tools plus about 35 everyday tools for products, pricing, readiness, inventory, sales, finance and settings) or Everything (every console tool your role allows). Some clients slow down or cap large tool lists, so start with Essentials; you can switch at any time under Profile → Connected apps without reconnecting, and tool names are the same in both sets.
If the client requested specific scopes you can only narrow them; if it requested none, sensible read defaults are pre-selected.
Scopes#
| Scope | Grants |
|---|---|
seller:products:read, seller:orders:preview, seller:orders:read, seller:keys:pull, seller:refunds:write, seller:webhooks:read, seller:promotions:read, seller:promotions:respond, seller:finance:read | The corresponding Seller API operations for the connected company, through a connector-managed API key |
console:catalog, console:inventory, console:network, console:promotions, console:sales, console:finance, console:analytics, console:integrations, console:settings | Read tools for the area (rolling out) |
console:write | Change tools, each guarded by an explicit confirmation (rolling out) |
offline_access | A refresh token, so the client stays connected |
Scopes never exceed your own role permissions: a scope only unlocks tools, every call is still authorized like a console action.
Tokens and lifetimes#
- Access tokens live one hour and are bound to the connector URL; they cannot be replayed against the Seller API directly.
- Refresh tokens rotate on every use. If a rotated token is presented twice, the whole connection is revoked as a precaution.
- Connections expire after 30 days without use and 90 days at most; reconnecting starts a new one.
Revoking access#
- You: Profile → Connected apps → Revoke. Revoking a connector-managed API key under Settings → API keys has the same effect.
- The client: standard token revocation with its refresh token.
- Avrix: blocked or removed accounts, suspicious reuse of tokens, or a client blocked platform-wide.
Revocation invalidates the tokens and the connector-managed key immediately; the assistant's next
call receives a 401 and the client asks you to sign in again.