Sellergoo MCP connector

https://sellergoo.com/api/mcp — Streamable HTTP transport, POST only. The server is stateless; each request carries its own authorization.

1. In Claude, open Settings → Connectors → Add custom connector.
2. Enter the URL https://sellergoo.com/api/mcp and continue.
3. Claude registers itself automatically (RFC 7591) and sends you to Sellergoo to sign in.
4. A consent screen names the client and the workspace it would read. Approve it, and Claude receives a token scoped to that one workspace.

Nothing is copied or pasted by hand, and no API key is involved. The consent screen names the workspace the connection will read, before you approve — check it. If you belong to more than one workspace, today the connection is always granted to the first one your account was added to, and there is no way to choose a different one from Claude. Write to us if you need a second workspace connected.

Nine tools, all read-only:

• Connected workspace get_me — Which workspace this connection reads, who approved it, and what it holds — the answer to “why are these figures empty?”.
• Sales channels list_channels — The marketplaces and stores connected to the workspace, and their sync state.
• Profit KPIs get_kpis — Sales, refunds, fees, COGS, ads, gross and net profit for a period.
• Profit & loss get_pnl — A month-by-month P&L, optionally for one channel.
• Orders list_orders — Orders in a date range, paginated, with each order's sales and marketplace fees.
• Products list_products — Per-SKU sales, margin and profit for a period.
• Marketplace payouts get_payouts — Settlements received from marketplaces and payment providers.
• Alerts list_alerts — Recent alert events — stock-outs, low stock, thin margins, lost Buy Box, price changes, negative reviews, sync failures.
• Inventory levels get_inventory — Stock on hand and days of cover per SKU.

Every tool is annotated readOnlyHint: true, so a client can see before calling that nothing will be modified. The connector has no write, no ordering, no shipping and no payment capability of any kind.

The connector uses OAuth 2.1 with PKCE (S256 required). The single scope is mcp:read. Tokens are bound to one user and one workspace: a token issued for your workspace can never read another, and access ends the moment you revoke it.

Access tokens expire after one hour and are renewed automatically with a rotating refresh token — a refresh token is single-use, and if one is ever replayed the whole grant is revoked. Only hashes are stored; a database copy could not be replayed against the API.

Discovery documents, for clients that read them:

• /.well-known/oauth-protected-resource (RFC 9728)
• /.well-known/oauth-authorization-server (RFC 8414)

Open Settings → API keys in Sellergoo and revoke the connection. The client's tokens stop working immediately — there is no grace period and no cached copy. Removing the connector in Claude has the same effect from the other side; doing both is belt and braces.

The connector returns data that already belongs to your workspace, in response to your own requests. Sellergoo does not send your data to the AI client except as the answer to a tool call you triggered, and does not use it to train anything. What the client then does with the answer is governed by that client's own terms — for Claude, Anthropic's.

Full detail in the privacy policy and the terms of service.

Any MCP client that supports Streamable HTTP and OAuth 2.1 dynamic client registration works the same way. For scripts and self-hosted setups where a browser consent flow is impractical, a Sellergoo API key (Settings → API keys) is also accepted as Authorization: Bearer mb_live_… against the same endpoint.

Something not working, or a tool returning figures you cannot reconcile? Write to [email protected] with the workspace name and roughly when it happened, and we will look at the request log.