MCP

Your storefront, drivable from Claude.

GemBoss speaks MCP, the Model Context Protocol. Connect it once and Claude can capture a reference store, plan a theme change, build an offer and read your funnel, calling GemBoss directly instead of you clicking through it.

Connect Claude Code →Docs

What you get

One connection, one workflow.

Build and change

Capture, theme generation, scoped theme patches, offers, advertorials, campaigns and approvals — you are shown the ones your account may actually call.

Measure

15 read-only analytics tools: the funnel, segments, devices, channels, campaign profit and ranked CRO hypotheses.

Stay in control

Every tool carries a risk level. The gate that stops a write is enforced by the server, not by the prompt.

In practice

Ask for the job, not the clicks.

# in a Claude Code session, once the server is connected Using the gemboss MCP server: run a capture digest for https://reference-store.example, then plan a product page change that moves reviews above the description. Show me the plan and the risk assessment. # stop before proposing anything.

What happens

It reads first. The capture digest and the change plan are both read-only. Nothing exists yet, so there is nothing to undo.
Then it drafts. A proposed patch is scoped, validated and previewable, and lives inside GemBoss. Your Shopify store is untouched.
You decide. Applying a patch or creating a theme needs a recorded approval, and it lands on an unpublished draft even then.

Setup

Three steps.

1
Add the server
One command in Claude Code — claude mcp add --transport http gemboss https://mcp.gemboss.com/mcp — or paste that same URL as a custom connector in Claude Desktop. No key to request.
2
Sign in and pick your stores
Claude opens your browser on the GemBoss sign-in, then a consent screen. Tick the stores Claude may act on. The credential it issues is scoped to you and to exactly those stores.
3
Run something read-only
Ask Claude for a capture digest. If a digest comes back, you are connected, and you have changed nothing to find out.

Boundaries

What it will not do.

Level	What it can do
`read`	Answer a question. Capture digests, change plans, patch validation, previews, the whole analytics family. Some record a report or a preview inside GemBoss; none write to Shopify.
`draft`	Create work inside GemBoss: a proposed theme patch, an offer strategy, an advertorial funnel. Never writes to Shopify.
`approval`	Apply a patch or create a theme, behind an approval, and only onto an unpublished draft theme. Publishing is not one of the tools.

Scoped per shop. A key carries the shops it may touch. A request for any other shop is refused before it reaches your data.
Analytics is read-only by construction. Those tools carry the workflow:read scope. Connect only that server and write access is not a question you have to think about.
Publishing stays yours. An approved change lands on a draft theme. Making it live is still a deliberate act in Shopify.

Point Claude at your store

Tell us the shop domain and we will issue a scoped key, with the base URL for your workspace.

Request access →