How Authentication Works

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 under the hood the first time you connect:

1
Client sends a request to /mcp
The server responds with 401 Unauthorized and a pointer to the OAuth discovery endpoint.
2
Client discovers the authorization server
Fetches /.well-known/oauth-authorization-server to learn the login and token endpoints.
3
A browser tab opens automatically
Your client opens /oauth/authorize in your default browser. This page redirects to Google login — not Amazon. SellerSheet identifies you by your Google account.
4
You see an "Authorize Connection" page
After Google login, SellerSheet shows a confirmation page with your email and the client name. Click Authorize.
5
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 never log in again unless you regenerate your key.

No API key to copy

For Claude Code, Claude Desktop, Cursor, and Windsurf — just paste the URL and click Authorize in the browser. The token is handled automatically.

No Amazon login required

SellerSheet already holds your Amazon SP-API credentials from when you set up your store in the dashboard. The MCP auth only identifies you as a SellerSheet user — via Google.

Before you connect

You need an active SellerSheet account with at least one Amazon store connected. Visit dashboard.sellersheetai.com to set that up first if you haven't already.

Claude Code

Run this one command in your terminal. Claude Code opens a browser tab for the Google authorization, then stores the token automatically.

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 Desktop

Go to Settings → Developer → Edit Config to open claude_desktop_config.json and add:

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

Restart Claude Desktop. On first use a browser tab opens for the one-click Google authorization.

Cursor

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 Google authorization flow described above. After you click Authorize, Cursor stores the Bearer token in its keychain and reuses it for all future sessions.

Tip: If Cursor does not open the browser automatically, check Settings → MCP and click the refresh icon next to the sellersheet entry to trigger the authorization flow.

Windsurf

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.

Coze

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.

Get your API key from dashboard.sellersheetai.com → SellerSheet MCP → Generate API Key. Then in Coze:

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

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

Codex (OpenAI)

OpenAI Codex CLI supports remote MCP servers via its configuration file. Add the following to ~/.codex/config.toml (or pass via the --mcp-server flag):

[[mcpServers]]
name = "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 authorize with your Google account. No API key is required.

Tip: Run codex --mcp-server sellersheet=https://sellersheetai.com/mcp to add it inline without editing the config file.

OpenClaw

In OpenClaw, open Settings → MCP Servers → Add Remote Server and enter the URL:

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

OpenClaw uses the same OAuth flow as Cursor and Windsurf — a browser tab opens on first use. No API key or token field required.

Your First Tool Call

Once connected, start every session with get_user_context. It returns your stores, plan, and 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.

Troubleshooting

"No Amazon stores connected"

You need to connect an Amazon Seller Central account first. Go to dashboard.sellersheetai.com → My Stores → Add Store. The MCP server uses the credentials you authorize there — no separate Amazon login is needed in your AI tool.

"Workspace not initialized"

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

401 Unauthorized after authorizing

This usually means the API key was regenerated from the dashboard after the client was authorized. Remove the MCP server from your client, re-add the URL, and go through the one-click Google authorization again.

Browser tab doesn't open in Cursor / Windsurf

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 initiates auth on the first tool invocation.

How to Connect SellerSheet MCP