Connect AI assistants to Seller Snap (MCP) | The Seller Snap Knowledge Hub

What you can do

Connect an AI assistant (claude.ai, ChatGPT, Claude Code, Cursor, VS Code and others) to SellerSnap so it can work with your listings, analytics and exports directly. The connection uses the Model Context Protocol (MCP), an open standard for linking AI assistants to outside tools.

Once connected, you can ask things like:

"List my SellerSnap stores."
"Show me the analytics for my US store."
"Create an export of my active listings."

The assistant sees the same stores you see in SellerSnap. What it can change depends on your role or API key (see below).

Choose how to connect

Assistant	How it connects	What you need
claude.ai, Claude desktop/mobile app, ChatGPT	Sign in with your SellerSnap account	Nothing; no API key See: Connecting claude.ai and ChatGPT
Claude Code, Cursor, VS Code, Claude Desktop (config file), n8n, custom agents	API key in a request header	A SellerSnap API key

Every method uses the same server URL, exactly as written:

https://api.sellersnap.io/mcp

Connect claude.ai or ChatGPT (sign in, no key)

These assistants connect by signing in to your SellerSnap account, so you never handle an API key.

claude.ai

Works in claude.ai and in the Claude desktop and mobile apps.

Open Settings → Connectors → Add custom connector.
Name it SellerSnap, paste https://api.sellersnap.io/mcp, and click Add. If asked about the OAuth client, keep Use Claude's published identity.
Click Connect, log in with your SellerSnap account and approve access.
In a chat, turn the SellerSnap connector on and ask: "List my SellerSnap stores."

On Claude Team and Enterprise plans, an Owner adds the connector once for the organization. Each member then just clicks Connect.

ChatGPT

Works on ChatGPT web with Plus, Pro, Business, Enterprise or Edu. On Business and Enterprise, a workspace admin must allow developer mode.

Open Settings → Apps (called Plugins in some versions) and turn on Developer mode. If you don't see it, search the settings for "Developer".
Click Create (or Add custom MCP server). Name it SellerSnap, choose Server URL, paste the URL, and set Authentication to OAuth.
Leave the advanced OAuth settings as discovered: don't enter a client ID or secret. Tick I understand and want to continue and click Create.
Log in with your SellerSnap account and approve access.
In a new chat, click +, turn on SellerSnap, and ask "Use SellerSnap to list my stores". ChatGPT asks you to approve each tool call.

What a signed-in connection can do

It sees the same stores you see in SellerSnap and can use every read tool.

Connected apps (claude.ai, ChatGPT) are read-only. They can't use the listing-change tools (update_price_bounds, update_min_profit_margin, set_repricing_status), update_listings or imports. To make changes from an assistant, connect it with an API key in a client such as Claude Code, Cursor or Codex (see below).

Disconnecting

Remove the connector in claude.ai or ChatGPT.
Access also stops for anyone whose SellerSnap user is removed or deactivated.
To cut a connection off immediately, contact support.

Add SellerSnap as a custom connector using the same URL, then sign in with your SellerSnap account and approve access.

What a signed-in assistant can do

Everyone: read listings, analytics and exports for the stores you can see in SellerSnap.
Account owners and admins: also change min/max prices, minimum margin, and repricing on/off. The assistant shows a preview first and changes nothing until you confirm.

Connect Claude Code, Cursor, VS Code and others (API key)

Step 1: Pick a key with the right role

Key role	What the assistant can do	When to use
Viewer	Read only	Recommended unless you want the assistant to make changes
Editor	Read, plus update listing prices and settings and create exports. Changes go live immediately.	Only when you want the assistant to act for you
Custom	Only the permissions you grant	Fine-grained control

Create a key in SellerSnap under API keys if you don't have one.

Step 2: Add SellerSnap to your assistant

In each example, replace YOUR_API_KEY with your API key.

Claude Code

Run this in your terminal:

claude mcp add --transport http sellersnap https://api.sellersnap.io/mcp \   --header "Authorization: Bearer YOUR_API_KEY"

Then run claude mcp list. It should show sellersnap … ✔ Connected.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{   "mcpServers": {     "sellersnap": {       "url": "https://api.sellersnap.io/mcp",       "headers": { "Authorization": "Bearer YOUR_API_KEY" }     }   } }

VS Code

Add this to .vscode/mcp.json. VS Code asks for your key once and stores it as a secret, so the key is not written into the file:

{   "inputs": [     {       "type": "promptString",       "id": "sellersnap-key",       "description": "SellerSnap API key",       "password": true     }   ],   "servers": {     "sellersnap": {       "type": "http",       "url": "https://api.sellersnap.io/mcp",       "headers": { "Authorization": "Bearer ${input:sellersnap-key}" }     }   } }

Claude Desktop (config file)

Use this only if you prefer an API key over the sign-in connector above. Add this to claude_desktop_config.json. Claude Desktop reaches remote servers through the mcp-remote bridge, so Node.js must be installed:

{   "mcpServers": {     "sellersnap": {       "command": "npx",       "args": [         "-y",         "mcp-remote",         "https://api.sellersnap.io/mcp",         "--header",         "Authorization:${SELLERSNAP_AUTH}"       ],       "env": { "SELLERSNAP_AUTH": "Bearer YOUR_API_KEY" }     }   } }

Keep Authorization:${SELLERSNAP_AUTH} without a space, exactly as above.

Other clients (n8n, custom agents, …)

Any MCP client that lets you set a request header can connect. Give it these three settings:

Setting	Value
Transport	HTTP (sometimes called streamable-http)
URL	`https://api.sellersnap.io/mcp`
Header	`Authorization: Bearer YOUR_API_KEY`

Step 3: Check that it works

Restart your assistant. Most only load MCP servers at startup.
Ask: "List my SellerSnap stores."
It should reply with your store names and marketplaces.

Viewer and Editor keys can list stores. A custom key needs the stores.read permission.

Keep your API key safe

Treat your API key like a password. Anyone who has it can access your SellerSnap data.

Don't paste it into shared files, chats or code repositories.
Prefer a Viewer key unless the assistant needs to make changes.
If a key leaks, revoke it on the API keys page and create a new one.

Troubleshooting

Problem	Fix
claude.ai or ChatGPT asks for an API key	They don't take a key. Add the connector with the URL only and sign in with your SellerSnap account.
The assistant doesn't see SellerSnap	Restart the assistant, and in claude.ai make sure the connector is turned on for the chat.
Claude Desktop config won't connect	Check Node.js is installed and that `Authorization:${SELLERSNAP_AUTH}` has no space.
"List my stores" fails with a custom key	Add the `stores.read` permission to the key.
The assistant can't change prices	Use an Editor key, or sign in as an account owner or admin.

For the full list of tools, permissions and limits, see the full MCP guide.