Connect an AI client
Add SellerSheet to the assistant you already use — one server URL, browser sign-in or an API key, the same tools in every client.
Your AI signs in to your SellerSheet account, sees only the stores you can see, and works through the same tools as the Google Sheets sidebar.
What you need
- A SellerSheet account with a connected store — Connect your store.
- An AI client that speaks MCP over Streamable HTTP — every client below does.
| Setting | Value |
|---|---|
| Server URL | https://sellersheetai.com/mcp |
| Transport | Streamable HTTP |
| Sign-in | OAuth in the browser (no key to copy) — or an API key as Authorization: Bearer <key> |
Fastest: Claude, Claude Code, Codex, ChatGPT, CodeBuddy or WorkBuddy? Install the plugin.
The SellerSheet plugin adds the skills and the MCP server in one step: add the GitHub repository sellersheetai/sellersheet-skills as a marketplace, then install the plugin from it. Each client's page below has the exact steps; every other client adds the server by hand.
Choose your client
Claude desktop & claude.ai
The plugin from Customize → Plugins, or a custom connector.
Claude Code
The plugin, or claude mcp add — then /mcp to sign in.
ChatGPT
The plugin in the desktop app, or the server by URL on chatgpt.com.
Codex
The plugin in the ChatGPT desktop app, or the Codex CLI.
Cursor
A global MCP server in Cursor Settings or mcp.json.
Windsurf
mcp_config.json with serverUrl.
Coze 扣子
An MCP tool with an API key in the header.
WorkBuddy
The plugin, from a marketplace added under 技能 → 套件.
CodeBuddy
The same plugin as Claude Code.
Qwen 千问
A custom connector in the QwenWork desktop app.
Any MCP client
The URL, the transport and the two ways to sign in.
Check it works
Ask: "Which stores can you see?" Your agent calls get_user_context and lists your store refs, such as myStore-US, with your plan and each store's status. Every session should start there.
How sign-in works
Your sign-in identifies you to SellerSheet with Google or an email code — never with Amazon. SellerSheet already holds the Amazon authorization you gave when you connected your store. Each browser sign-in creates an MCP key under Settings → API & MCP in the app, named after the client; delete it there and that client stops working at once.
If something's off
| Symptom | Fix |
|---|---|
| "Unauthorized" (401) | Your sign-in or key expired or was deleted. Sign in again, or create a new key. |
| The browser never opens | Update the client — older versions don't support MCP sign-in — or use an API key. |
| "No stores" | Connect a store first: Connect your store. |
| Tools time out | Some Amazon reports take a minute or two. Raise your client's MCP tool timeout. |
More in Troubleshooting. Next: Install the skills, or call the same tools from code.