How to Connect SellerSheet MCP

SellerSheet provides an MCP server that gives the AI client you already use — Claude, ChatGPT/Codex, Cursor and others — more than 400 tools for your Amazon and noon stores. This guide connects it to Claude Code, Claude Desktop, Cursor, Windsurf, Coze and Codex.

How authentication worksCopy Anchor Link

The SellerSheet MCP server is a standard OAuth 2.0 remote MCP endpoint at https://sellersheetai.com/mcp. You do not need to copy an API key or configure any tokens manually for most clients. Here is what happens the first time you connect:

1. Your client sends a request to /mcp. The server responds with 401 Unauthorized and a pointer to the OAuth discovery endpoint.
2. The client discovers the authorization server. It fetches /.well-known/oauth-authorization-server to learn the login and token endpoints.
3. A browser tab opens automatically. Your client opens the SellerSheet sign-in page in your default browser. You sign in to SellerSheet — with Google, or with a code sent by email — not to Amazon.
4. You see an "Authorize Connection" page. After signing in, SellerSheet shows a confirmation page with your account and the client name. Click Authorize.
5. The client receives and stores the Bearer token. The client exchanges the authorization code for a Bearer token and saves it locally. All future requests use this token silently — you do not sign in again unless the connection is revoked.

Claude CodeCopy Anchor Link

Run this one command in your terminal, then start Claude Code and run /mcp to sign in — your browser opens the SellerSheet sign-in and Claude Code stores the token.

claude mcp add --transport http sellersheet https://sellersheetai.com/mcp

Alternatively, add it to your project's .mcp.json:

{
  "mcpServers": {
    "sellersheet": {
      "type": "http",
      "url": "https://sellersheetai.com/mcp"
    }
  }
}

Claude DesktopCopy Anchor Link

1. Open Settings → Connectors → Add custom connector.
2. Name it SellerSheet and paste https://sellersheetai.com/mcp as the server URL.
3. Click Connect — your browser opens the SellerSheet sign-in; approve, and you're back in Claude.

The same steps work on claude.ai in the browser (custom connectors need a paid Claude plan).

CursorCopy Anchor Link

Go to Cursor Settings → MCP → Add new global MCP server and paste the config below, or add it directly to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "sellersheet": {
      "url": "https://sellersheetai.com/mcp"
    }
  }
}

There is no API key or token field in the config — Cursor handles OAuth automatically. When you first use a SellerSheet tool in a Cursor chat, Cursor detects the 401 from the server, reads the OAuth metadata, and opens your browser for the authorization flow described above. After you click Authorize, Cursor stores the Bearer token and reuses it for all future sessions.

WindsurfCopy Anchor Link

Edit ~/.codeium/windsurf/mcp_config.json (or open Windsurf Settings → MCP Servers → Add Server):

{
  "mcpServers": {
    "sellersheet": {
      "serverUrl": "https://sellersheetai.com/mcp"
    }
  }
}

Same OAuth flow as Cursor — no token to copy. A browser tab opens the first time Windsurf calls a SellerSheet tool.

CozeCopy Anchor Link

Coze does not run a browser OAuth flow — it calls MCP endpoints directly from its servers. You need to provide your SellerSheet API key as a Bearer token in the request header.

Create an API key in the SellerSheet app under Settings → API & MCP. Then in Coze:

1. Open your Coze Bot → Skills → MCP Tool → Add MCP Tool.
2. Select Connect via URL.
3. Enter https://sellersheetai.com/mcp.
4. Add a custom header: Authorization: Bearer <your-api-key>.
5. Save and publish.

{
  "name": "SellerSheet MCP",
  "url": "https://sellersheetai.com/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY_HERE"
  }
}

Codex (OpenAI)Copy Anchor Link

The OpenAI Codex CLI supports remote MCP servers through its configuration file. Add the following to ~/.codex/config.toml:

[mcp_servers.sellersheet]
url = "https://sellersheetai.com/mcp"

Codex follows the same OAuth 2.0 flow — a browser tab opens on the first SellerSheet tool call and you sign in to SellerSheet and authorize. No API key is required.

Your first tool callCopy Anchor Link

Once connected, start every session with get_user_context. It returns your stores (with the ready-made store refs such as myStore-US that every store tool takes), your plan and your workspace config — the context every other tool depends on.

Call get_user_context to load my SellerSheet workspace,
then show me all active FBA shipments.

TroubleshootingCopy Anchor Link

"No Amazon stores connected"Copy Anchor Link

You need to connect an Amazon Seller Central account first. Sign in at sellersheetai.com and go to Settings → Stores & Marketplaces. The MCP server uses the authorization you grant there — no separate Amazon login is needed in your AI tool.

"Workspace not initialized"Copy Anchor Link

Open Google Sheets → Extensions → SellerSheet → Open Sidebar and complete the workspace setup. This creates the Drive folder structure the MCP server writes reports into. See Install & first sync.

401 Unauthorized after authorizingCopy Anchor Link

This usually means the key or connection was revoked under Settings → API & MCP after the client was authorized. Remove the MCP server from your client, re-add the URL, and go through the authorization again.

Browser tab doesn't open in Cursor / WindsurfCopy Anchor Link

Make sure your client version supports MCP OAuth 2.0. In Cursor, go to Settings → MCP and click the refresh/reconnect icon next to the sellersheet entry to trigger the flow manually. In Windsurf, restart the IDE after saving the config — it starts the authorization on the first tool call.

For every tool and the Tool API, see MCP & API.