Connector · MCP

Connect any AI agent to your business

Rexium exposes your Business over the open Model Context Protocol. One endpoint — mcp.rexium.ai — works with Claude, Cursor, ChatGPT, VS Code, Grok and any MCP client. Your agent reads the live catalog and custom fields through the same dispatcher your widget uses — no separate sync, no embedding drift.

Connect your agent (under 60 seconds)

One endpoint, every MCP client. Pick yours — the only thing that changes is where you paste the URL.

Availability: Claude Pro, Team & Enterprise

  1. 1
    In Claude.ai open Settings → Connectors → Add custom MCP server.
  2. 2
    Paste the Rexium endpoint and save.https://mcp.rexium.ai
  3. 3
    Claude opens the Rexium consent screen — pick the Business and the minimum scopes, then authorise.
  4. 4
    Ask Claude about your store. It calls search_commerce_catalog against your live catalog index (custom fields included) — no sync, no stale data.

What your agent can do once connected

  • Read your catalog. Query products by attribute (including your custom fields), check stock, list active discounts.
  • Tag contacts. Apply or remove semantic tags on Layer 2 Contacts based on signals it reasoned about (“tag everyone who left a 5★ review as VIP”).
  • Apply cart discounts. Validate a discount code against a cart, surface savings to the buyer, apply on confirmation.
  • Adjust prices. Mutate product prices with audit trail — every change is logged and reversible.

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 contract

Protocol
Model Context Protocol (MCP), JSON-RPC over streamable HTTPS.
Endpoint
https://mcp.rexium.ai

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

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 honours the Idempotency-Key header (24h TTL). Safe for SDK retries.
Rate limits
X-RateLimit-Limit · X-RateLimit-Remaining · X-RateLimit-Reset on every response. Honour these to back off proactively.

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