Connector · MCP

Add Rexium AI to Claude

Connect your Rexium AI Business to Claude.ai as a custom Model Context Protocol server. Claude reads your live catalog and Spine.3 custom fields through the same dispatcher your widget uses — no separate sync, no embedding drift.

Setup (under 60 seconds)

  1. 1

    Open Claude.ai Connectors

    In Claude.ai go to Settings → Connectors → Add custom MCP server. Available on Claude Pro and Claude Team workspaces.
  2. 2

    Paste the Rexium MCP endpoint

    https://mcp.rexium.ai

    Single endpoint serves every Rexium Business — the OAuth flow scopes the session to the Business you authorise.

  3. 3

    Authorise the scopes you want

    Claude opens the Rexium consent screen. Pick the Business you want to expose and the minimum scopes required (read-products, write-discounts, etc.). Re-grant anytime from your Integrations page.
  4. 4

    Ask Claude about your store

    Try: "Quais os meus 3 produtos com vintage anterior a 2010 ainda em stock?" — Claude uses search_commerce_catalog to query your Spine.3-aware index and answers with the live catalog. No knowledge-base sync; no stale data.

What Claude can do once connected

The complete tool catalog is published per-Business at {your-store}/.well-known/rexium-agent.json. Tools are scoped — the consent screen lists exactly what each tool needs.

Technical details

Protocol
Model Context Protocol (MCP) 2024-11-05, JSON-RPC over HTTPS.
Auth
OAuth 2.1 + PKCE (S256). Bearer Firebase ID token also accepted for development.
OAuth discovery
https://us-central1-rexium-ai.cloudfunctions.net/.well-known/oauth-authorization-server
Idempotency
Every mutating tool honors the Idempotency-Key header (24h TTL). Safe for SDK retries.
Rate limits
X-RateLimit-Limit · X-RateLimit-Remaining · X-RateLimit-Reset on every response. Honor these to back off proactively.

Questions or issues? See our docs or email support@rexium.ai. Privacy policy: rexium.ai/privacy · Terms: rexium.ai/terms.