Founding cohort pricing is open: Pro at today's price, locked while you stay. Limited seats. See the offer

Connect Claude Code

One command declares the server, and /mcp signs you in through your browser, as Claude does. A static key is there for the machine with no browser to open.

OAuth 2.1Static key for CIRead-onlyFree

Connect your store Read the Shopify MCP reference

Steps

Four minutes, start to finish

In the dashboard, open your store's settings, then Connectors, and copy the URL from External LLM Access. The id in it is the store's id, not the slug in your dashboard URL.
Run the command below. To share the server with your team, commit the .mcp.json shape under it: it holds the URL and no secret.
In Claude Code, run /mcp, pick boostecom and authenticate. Your browser opens on the BoostEcom consent screen: approve the scopes you want this client to have.
Ask for the store: getStoreContext returns plan, currency, markets, locales, themes and your granted scopes in one call.

Claude Codebash

OAuth 2.1

claude mcp add --transport http boostecom https://www.boostecom.app/api/mcp/v1/<STORE_ID>

# Then, in Claude Code: /mcp, pick boostecom, authenticate.

# Or commit it with the project, in .mcp.json. Only the URL is
# committed: each developer signs in with their own account.
# {
#   "mcpServers": {
#     "boostecom": { "type": "http", "url": "https://www.boostecom.app/api/mcp/v1/<STORE_ID>" }
#   }
# }

# Headless (CI, no browser): a static key, read from the environment.
# claude mcp add --transport http boostecom https://www.boostecom.app/api/mcp/v1/<STORE_ID> \
#   --header "Authorization: Bearer ${BOOSTECOM_MCP_KEY}"

What to paste

Replace <STORE_ID> with your store id. The dashboard shows the same URL fully resolved, next to the key.

Gotchas

What bites

Each developer signs in with their own BoostEcom account, so a teammate who leaves the organization loses access at their next call, with no key to rotate.
A static key never passed a consent screen, so it opens the relay and nothing else: the 15 read-only Shopify tools, within what the Custom App allows. The documentation tools, Studio and your store's intelligence record need the OAuth sign-in. Keep a key for CI and headless runs, read from an environment variable, never written in a committed file.
A tool you expected and cannot see was refused by one of two gates: the scopes you approved, or what the Custom App granted. Call it anyway and the refusal names which one.

Claude Code's own documentation

Other clients

3 other clients, tested end to end

The full reference: tools, scopes, discovery

Ask @Atlas about the store you connect

The same store Claude Code reads is one question away here. Ask it in your own words.

Read the Shopify MCP reference