Do I need an API key?

No. You press Connect to Claude on SellerClaw’s listing in the Claude Directory, sign in in the browser and approve access. Claude registers itself with SellerClaw, so there is nothing to paste.

Does this work on my phone and in Cowork?

Yes. The connector is attached to your Claude account, so the same one works in the browser, on your phone, in the desktop app and in Cowork. You add it once.

Can Claude send email or spend ad budget on its own?

Not by default. Money and outbound email still wait for your yes in SellerClaw, whether the request came from Claude, ChatGPT, a scheduled task or SellerClaw’s own chat. You can change that per connection under Your team → Connected apps.

I am on a Claude Team plan and cannot add a connector.

On a team or enterprise Claude account only an owner can add connectors. Until they do, the option is not offered to you. Ask the owner to connect SellerClaw from the Claude Directory (or add https://mcp.sellerclaw.ai/mcp as a custom connector), then sign in with your own SellerClaw account when Claude opens the consent screen.

Does this replace SellerClaw’s own chat?

No. The agents keep working in SellerClaw. The connector lets the Claude you already have open look in, ask, and act on the same account.

Documentation

SellerClaw MCP for Claude

SellerClaw is a team of AI agents connected to the stores you sell on — Shopify, eBay, Amazon — plus suppliers and ad accounts. This page is how to drive that same account from Claude, instead of opening another dashboard.

SellerClaw is in the Claude Directory: open the listing and press Connect to Claude. The address below is for adding it by hand and for other clients.

Remote MCP server URL

https://mcp.sellerclaw.ai/mcp

The same address for every Claude surface. Claude reads the sign-in settings from it — you do not fill in a client id or secret.

Before you start

A SellerClaw account with at least one store connected.
A plan that allows an outside assistant. Signing up is free; putting the agent — and this connector — to work is a plan.
Claude on claude.ai, Claude Desktop, Claude mobile, or Cowork. On a Team or Enterprise Claude workspace, only an owner can add connectors.

Connect SellerClaw in Claude

Two steps. There is no install, no config file, and no API key.

Connect SellerClaw to Claude: step-by-step setup — The whole path in one minute — signing up, starting the plan, connecting, and Claude's first answer about a store. · Watch on YouTube

1
Open SellerClaw in the Claude Directory
Open SellerClaw’s listing and press Connect to Claude. Inside Claude it is also under Customize → Connectors, on the Discover tab. Claude lists it as a community connector, published by SellerAI, Inc.
2
Sign in and approve access
Claude sends you to SellerClaw. Sign in if asked, then approve access once. The connector then follows your Claude account — browser, phone, desktop and Cowork.

Adding it by hand

If the directory is not available in your Claude workspace, add SellerClaw as a custom connector. Open Customize → Connectors, press Add, name it SellerClaw and paste the address from the top of this page. Leave the two OAuth fields under Advanced settings empty — Claude fills those in from the address. Then sign in and approve access as above.

The two OAuth fields under Advanced settings stay empty — Claude reads the sign-in settings from the address itself.

What Claude can do

Five tools, which Claude composes into the same commands SellerClaw’s own agents use — listings, orders, ads, suppliers, research:

sellerclaw_guide — a short task recipe with ready-to-run calls.
sellerclaw_groups — what command groups exist.
sellerclaw_describe — the exact fields one command needs.
sellerclaw_read — run a command that only reads.
sellerclaw_write — run a command that changes something.

In Claude you set each tool to allow, ask every time, or block. Money and outbound email still wait for your yes inside SellerClaw, even when Claude is the one that asked — see how approvals work. Revoke the connection under Your team → Connected apps and that app is out of your account the same second.

The middle icon on each row is ask-me-every-time, and it is where anything that changes something starts out.

How sign-in works

The server is not open. Claude connects to https://mcp.sellerclaw.ai/mcp, discovers SellerClaw’s authorization server, and registers itself with OAuth 2.0 Dynamic Client Registration (RFC 7591) and PKCE S256. You then see SellerClaw’s consent screen. After you approve, Claude holds a token for your account and sends it on every tool call.

You never copy a client id, a secret, or an API key. A token in the connector URL is not used and not supported.

ChatGPT, Desktop, Code and the CLI

The hosted address above is what the Claude connector uses. The same account can be reached a few other ways — pick one, you do not need all of them.

ChatGPT

Custom plugins, paid ChatGPT plan. Turn on Developer mode in Settings → Security and login, add a plugin, paste the same address, leave Authentication on OAuth. On Business or Enterprise an admin has to allow custom plugins first. The walkthrough with screenshots is in Bring Your Own Assistant.

Claude Desktop extension

A one-file install for this computer only, if your workspace does not allow custom connectors. Download sellerclaw.mcpb, open it with Claude Desktop. The first tool call opens a browser to sign in. No Python, no command line.

Claude Code

Install the SellerClaw plugin from the marketplace — tools and task skills in one:

Add the marketplace

/plugin marketplace add sellerai-com/sellerclaw-cli

Install the plugin

/plugin install sellerclaw@sellerclaw

On first use it opens your browser to sign in.

Command line

The same surface as a local MCP server, for Cursor or any other client. Install sellerclaw-cli, run sellerclaw auth login, then sellerclaw mcp.

For IT admins

This is the page to review before allowing the connector in a Claude Team or Enterprise workspace.

Server URL: https://mcp.sellerclaw.ai/mcp
Transport: Streamable HTTP. Every user connects to the same URL.
Authentication: OAuth 2.0 with Dynamic Client Registration (RFC 7591). PKCE S256 required. Authorization server metadata at https://api.sellerclaw.ai/.well-known/oauth-authorization-server. Redirect URI used by Claude: https://claude.ai/api/mcp/auth_callback.
Enterprise managed auth: Not supported. Each user signs in to SellerClaw through the standard consent screen. Directory connectors use one shared OAuth application; access is scoped by that user’s own SellerClaw permissions.
Data accessed: Whatever the signed-in SellerClaw user can already see and change: store catalogs, listings, orders, ads, suppliers. Claude does not receive a broader token than that account. Marketplace data (Shopify, eBay, Amazon) is read through connections the seller already authorized in SellerClaw.
Revoke: SellerClaw → Your team → Connected apps → Revoke. Takes effect immediately.
Privacy: sellerai.com/privacy-policy
Support: hello@sellerai.com
Publisher: SellerAI, Inc. · 169 Madison Avenue STE 81650, New York, NY 10016, United States

If it does not connect

Claude does not let you connect it: You are on a Claude Team or Enterprise plan and you are not an owner. Ask an owner to connect SellerClaw, or connect it on a personal Claude account.
Claude never opens the SellerClaw sign-in: Allow pop-ups for claude.ai. If you added it by hand, check the URL is exactly https://mcp.sellerclaw.ai/mcp — including /mcp at the end.
Tools appear, but every run fails: The connector listed, but the account did not finish consent, or the SellerClaw plan does not allow an outside assistant. Open Your team → Connected apps: the status card says whether anything has actually signed in. Choose a plan if the page tells you to.
Wrong SellerClaw account: Revoke the connection in SellerClaw, then connect SellerClaw in Claude again and sign in as the right user on the consent screen.

Common questions

Start for Free