Skip to content

Connect your AI agent

Crossmart works with any AI agent that speaks the Model Context Protocol (MCP). Once connected, the agent can look up products and stock, create and edit products, publish them to your stores and fix listings that need details, read orders and reports, and ask Crossmart’s AI for content that you then approve.

Server URL https://mcp.crossmart.io/mcp (Streamable HTTP)
Authentication OAuth sign-in, or an API key in x-api-key or Authorization: Bearer <key>
Tools Products, stock, stores, listings, eBay, orders, reports, content, Ask

The MCP server reference lists every tool.

Your agent’s changes wait for you: by default nothing it changes applies until you approve it under Agent proposals, and it can read freely meanwhile.

Don’t want to set up an agent? Crossmart Agent is an agent inside Crossmart with the same tools. It proposes every change for you to approve.

Connect your stores in the dashboard (Channels). Agents can’t connect stores: the marketplace asks you to approve access yourself.

The simplest way: add the server’s URL to your agent, then sign in to Crossmart in the browser. No key is copied or pasted, and each person connects with their own account.

  1. Add https://mcp.crossmart.io/mcp to your agent without a key. For Claude Code:

    Terminal window
    claude mcp add --transport http crossmart https://mcp.crossmart.io/mcp

    Then, in a Claude Code session, run /mcp, choose crossmart and Authenticate.

  2. Your browser opens Crossmart. Sign in, and choose the workspace the agent works in.

  3. Review what the agent asks for, and choose Everything it asks for or Read only (it can look, but not change anything). Approve.

The agent then works in that workspace only, and never with more than your own role allows. It can never manage members, API keys, store connections, settings or billing.

See and disconnect your agents under Settings → Connected agents. Disconnecting signs the agent out at once.

Access the agent asks for It lets the agent
Catalog, read See products, stock, stores and AI suggestions
Catalog, write Create and change products, prices and stock
Orders, read See orders
Stores, write Add products to stores and take them off
Reports, read See sales and stock reports
Suggestions, write Ask for AI content and approve suggestions

Read-only access keeps the three read permissions.

For agents that can’t sign in, or for scripts and shared setups, use a workspace API key.

  1. In the dashboard, open Settings → API keys and create a key. Name it after the agent so it’s easy to find and revoke.

  2. Pick the smallest role that works:

    • Viewer: questions only (“which products are low on stock?”).
    • Editor: also edit products and stock, publish to stores and generate content. AI content still waits for a person to approve it.
    • Approver or Admin: may also approve suggestions. Give an agent this only on purpose.
  3. Put the key in the agent’s configuration or in an environment variable (CROSSMART_API_KEY). Never paste it into a chat.

A key works in exactly one workspace. See Roles and permissions.

Each guide was checked against the platform’s official documentation on 2026-11-06. “Unverified” means the official docs don’t confirm every detail; the guide says which.

Agent OAuth sign-in API key header Skill Status
Claude Code Yes Yes Yes Verified
Claude Desktop Yes (custom connector) Through a local bridge Upload (zip) Verified
claude.ai Yes Beta organizations only Upload (zip) Verified
ChatGPT Yes No No Verified
Cursor Yes Yes Verified
Windsurf (Devin Desktop) Yes Yes Verified
VS Code (GitHub Copilot) Yes Yes Verified
Zed Yes Yes (Authorization: Bearer) Yes Verified
Cline Yes Yes Verified
Continue Probably No Unverified
OpenAI Codex CLI Yes Yes Verified
Gemini CLI Yes Yes Verified
OpenClaw Yes Yes Verified
Meta Muse Reported Not documented No Unverified
Goose Yes (goose configure) Yes Unverified
Hermes Agent Yes Yes Verified

An empty OAuth cell means the guide covers the API key. Many of these clients can also sign in to MCP servers with OAuth: add the URL without a key and follow the client’s own sign-in prompt.

The Crossmart skill teaches an agent the seller workflows on top of the tools.

Once connected, ask the agent things like:

  • “Which products are out of stock, and on which stores are they listed?”
  • “Create a draft product for a blue ceramic mug at $18 with 25 in stock.”
  • “Add every active mug to my Shopify store.”
  • “Which of my eBay listings failed, and what do they need?”
  • “How did sales in the last 7 days compare with the week before?”
  • “Write better titles for my 10 best sellers on eBay.” (they arrive as suggestions to approve)
  • The server won’t connect (HTTP 401): the client sent no key and didn’t sign in. Check the header name and that the environment variable is set where the client runs, or sign in with OAuth.
  • Tools answer Crossmart refused (401): the key is wrong or revoked, or the agent was disconnected. Create a new key, or sign in again.
  • 403 Requires the … permission: the key’s role, or the access you approved, is too small for that tool.
  • The client asks you to sign in although you set a key: it found no Authorization header and started OAuth. Sign in, or send the key as Authorization: Bearer <key> (see Zed).
  • Another platform: any client that can send a header to a Streamable HTTP server works. Write to [email protected] and we’ll add a guide.