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 Code, Codex or CodeBuddy? Install the plugin.
The SellerSheet plugin adds the skills and the MCP server in one step — see Install the skills. The pages below are for setting it up by hand, and for every other client.
Choose your client
Claude desktop & claude.ai
A custom connector, signed in in the browser.
Claude Code
One command, then /mcp to sign in.
ChatGPT
A custom connector in developer mode.
Codex
The plugin, or codex mcp add.
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
From the connector marketplace — no command.
CodeBuddy
The same plugin as Claude Code.
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.