Connect Claude Code to GemBoss

GemBoss speaks MCP, the Model Context Protocol. Once Claude Code is connected, Claude can call GemBoss directly: capture a reference storefront, plan a theme edit, read your conversion funnel. You stay in the loop at every gate that changes anything.

What you need first

A GemBoss account, and Claude Code installed. That is the whole list — there is no key to request and no base URL to be told. You sign in through your browser during the connection and GemBoss issues the credential itself, scoped to you and to the stores you pick.

No account yet? Start at gemboss.com — describe your store, watch it get built, then keep it. That gives you the account this page needs.

Add the server

One command. Run it wherever you want Claude Code to reach GemBoss.

Then, in a Claude Code session, run /mcp and choose to authenticate. Your browser opens on the GemBoss sign-in, and then on a consent screen listing the stores you can grant. Tick the ones Claude may act on and approve. Claude Code holds the token from there.

The same screen has a second choice, and it decides how much you see:

Leave it off if you are working on pages; a shorter list is a Claude that picks the right tool more often. Tick it if you want Claude cloning a reference store or running campaigns. To change your mind, reconnect and answer it differently — and if the page tools look missing for a moment right afterwards, ask Claude to list its tools again.

Use --scope user if you want the server available in every project rather than just the current directory.

The token is bound to the stores you ticked, so a request for any other store is refused before it reaches that data. Publishing stays a separate, human decision — see what Claude can and cannot change.

Check it worked

You want to see gemboss and a green connected marker. If Claude answers questions but never calls a tool, the connection is the first thing to rule out, not the prompt.

Then ask Claude, inside a session:

List the tools available on the gemboss MCP server, grouped by whether they can change anything.

You get back the tools your account is entitled to, in three families. gem.* covers capture, planning, offers, campaigns, research and approvals. gemtheme.* covers theme generation and patching. gemboss.* covers page building and the read-only analytics. The list is filtered to what your token may actually call, so two people can see different lengths and both be correct.

A safe first request

Nothing below writes to Shopify.

Run a capture digest for https://example.com and summarise what GemBoss would be able to rebuild from it. Do not create any workflow.

If that returns a digest, you are connected properly.

Next

• What Claude can and cannot change
• Clone a reference store