Connect an assistant

Any AI client that speaks the Model Context Protocol (MCP) — Claude, Cursor, or another MCP-compatible tool — can read your workspace's own seller data once you connect it. It answers questions about your profit, orders, and catalog the same way a report on screen would; it never changes anything.

What it can do

Once connected, an assistant can:

• Report daily profit, a SKU profit ranking, and a period profit & loss, using the same computation the in-app reports use.
• Summarize unlinked listings and unprocessed orders that need attention.
• Answer a narrower question about your own orders, returns, or catalog with a filtered lookup.
• Fall back to a guarded, read-only SQL query for something the tools above can't express, limited to the tables and columns in your own workspace.

What it can't do

• Create, update, or delete anything. Every tool is read-only — there is no write path an assistant can reach.
• See another workspace's data. Every connection is bound to exactly one workspace at authorization time; no tool accepts a workspace or tenant id as an argument, so there's nothing for an assistant to point at another seller's data even by mistake.
• Export everything at once. Every response is bounded — a page of rows, a capped result set, a row limit and cost budget on the SQL fallback — so there's no unbounded dump of your data.

How to connect

From Settings → AI connections, copy the endpoint and either:

• Authorize via OAuth (recommended) — a client that supports it prompts you to sign in and pick a workspace, and the resulting connection is scoped to just that workspace.
• Create a manual token — a fallback for a client that doesn't support OAuth yet. Paste it into the client's configuration as a bearer token.

Either way, the same page lists every connection you've authorized and lets you revoke one — doing so takes effect immediately, with no grace period.