Connect Claude Desktop to GemBoss
Paste one URL into Claude's connector settings. No key, no JSON editing.
Claude Desktop connects to GemBoss as a custom connector. You sign in through your browser during setup and GemBoss issues the credential itself, scoped to you and to the stores you pick — there is no key to request and no config file to edit.
Add the connector
In Claude, open Settings → Connectors → Add custom connector, and give it this URL:
Claude opens the GemBoss sign-in, then a consent screen listing the stores you can grant. Tick the ones Claude may act on and approve. The connector shows as Connected when it is done, and its tools are available in any chat.
That screen also asks whether you want the build tools — theme generation, campaigns, offers and competitor research. Unticked, the connector carries your pages and analytics, around 60 tools. Ticked, it carries around 50 more. Leave it off unless you want Claude cloning stores or running campaigns; you can reconnect and answer differently later.
No account yet? Start at gemboss.com — describe your store, watch it get built, then keep it. That gives you the account this step needs.
If you were issued a static key
Older workspaces were given a gb_mcp_ key before the connector existed. Those keep working,
and the command below writes the local bridge for them. If you are setting up today, use the
connector above instead.
To keep the key out of your shell history, pipe it in instead:
The command writes a local bridge for Claude Desktop, merges the server into your Claude Desktop config, points it at the live endpoint, verifies that the endpoint answers and has the tools it expects, and redacts the key in anything it prints.
Restart Claude Desktop afterwards. The config is read at launch, so an unrestarted app will show no tools and look like a failed setup.
Options worth knowing
| Option | What it does |
|---|---|
--key-stdin |
Read the key from stdin instead of the command line |
--shop-id |
The one shop domain this connection may act on |
--server-name |
Name the connector something other than the default |
--dry-run |
Print what would be written, change nothing |
--skip-verify |
Skip the live check, for offline setup |
Run npx @gempages/claude-mcp help for the full list.
Check it worked
Open Claude Desktop and ask:
Use the GemBoss MCP server. List the available tools, then run a capture digest for https://example.com. Do not approve or publish anything.
One connection per person
Each person connects as themselves. The credential carries the stores that person ticked, and that is the boundary that keeps one person's session from reaching another store — so do not share a connection, and do not hand a static wildcard-shop key to an external user.
Next
Stuck on the connection?
You connect at https://mcp.gemboss.com/mcp and sign in through your browser — there is no key to ask for. If the browser step does not finish, the troubleshooting page walks through what to check.
Thanks. That goes straight to the people who write these.