Plug your Shopify store into Claude and ChatGPT.

A remote MCP server, one per store. Every store you connect to BoostEcom gets its own endpoint, speaking Model Context Protocol over streamable HTTP. Any client that speaks MCP (Claude, ChatGPT, Claude Code, Cursor, or one you wrote yourself) can discover it, authorize against it and call its tools.

Your Shopify credentials never leave our servers. The client holds a BoostEcom token; the short-lived Shopify token the BoostEcom app delegates stays with us, encrypted at rest. Revoke the BoostEcom token and the client is out, without ever having seen a Shopify secret.

• MCP, from your AI clientClaude, ChatGPT, Claude Code and Cursor read the store live, over OAuth or a static key. Read-only.
• The dashboard, with @AtlasThe one place where writes happen, each behind your approval. Same store, same BoostEcom app.
• Intelligence, from your client or your codeThe Shopify store graph has its own MCP server and a read-only REST API with a bei_ key. Market data, never your store's.
• A public UCP profileWhen BoostEcom reads another store's public catalog, it presents this profile: catalog search and lookup only, no cart, no checkout, no secret.

https://www.boostecom.app/api/mcp/v1/<STORE_ID>

https://www.boostecom.app/api/mcp/intelligence

https://www.boostecom.app/.well-known/ucp-agent

You install the BoostEcom app from your Shopify admin and choose in the app what it may access. Your grant is the ceiling: we add no access of our own.

• OAuth 2.1 with PKCE, no client secret to keep
• Each token opens one store and is hashed at rest
• A static key for CI and headless runs

https://www.boostecom.app/api/mcp/v1/<STORE_ID>

GET https://www.boostecom.app/.well-known/oauth-authorization-server
GET https://www.boostecom.app/.well-known/oauth-protected-resource/api/mcp/v1/<STORE_ID>
GET https://www.boostecom.app/api/mcp/<STORE_ID>/.well-known/oauth-protected-resource

1. 1

   Your client calls the endpoint without a token and gets a 401 whose WWW-Authenticate header points at our discovery documents (RFC 9728).

2. 2

   It reads the protected-resource document, which names this origin as the authorization server.

3. 3

   It reads the authorization-server metadata (RFC 8414) to find the register, authorize, token and revocation endpoints.

4. 4

   It identifies itself with a Client ID Metadata Document, an https URL we fetch and verify, or through dynamic registration (RFC 7591). No secret is issued and PKCE S256 is mandatory.

5. 5

   You approve a consent screen that lists the permissions in plain words, showing only the ones your grant to the BoostEcom app can satisfy.

6. 6

   The client trades its one-time code for an access token that expires after 60 minutes, and a refresh token that rotates on every use.

7. 7

   A tool outside the grant answers 403 with the exact scope to ask for: the client re-authorizes for that one scope and retries.

8. 8

   Disconnect the client and it calls the revocation endpoint (RFC 7009): the token dies on our side too, not only in the client's memory.

Each token opens one store: a token issued for store A is refused on store B, and organization membership is checked again on every call. Tokens are stored as SHA-256 hashes, never in a form we could read back.

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="BoostEcom MCP",
  resource_metadata="https://www.boostecom.app/.well-known/oauth-protected-resource/api/mcp/v1/<STORE_ID>",
  scope="boostecom:store.read boostecom:catalog.read …"

{
  "access_token": "<ACCESS_TOKEN>",
  "token_type": "Bearer",
  "expires_in": 3600,
  "refresh_token": "<REFRESH_TOKEN>",
  "scope": "boostecom:store.read boostecom:catalog.read"
}

HTTP/1.1 403 Forbidden
WWW-Authenticate: Bearer error="insufficient_scope",
  scope="boostecom:orders.read",
  resource_metadata="https://www.boostecom.app/.well-known/oauth-protected-resource/api/mcp/v1/<STORE_ID>"

• Mutations refused before Shopify sees them
• Every write attempt lands in your audit log
• Changes go through the dashboard approval flow

tools/call shopifyAdminGraphQL

mutation {
  productUpdate(product: { id: "gid://shopify/Product/1", title: "New title" }) {
    product { id }
  }
}

{
  "isError": true,
  "content": [
    {
      "type": "text",
      "text": "Refused: this mutation is classified destructive (product/price updates, discounts, inventory, …). This connector is read-only: every write requires human approval. Run it from the BoostEcom dashboard chat, where the approval flow lives."
    }
  ]
}

• State of the storeOne runAudit call returns the shop, its themes and a product sample together, so the model reasons over the whole store instead of stitching four requests.
• Catalog questionsWhich products are still drafts, what is out of stock, which handles collide: answered against live data, not a stale export pasted into a chat.
• Anything the Admin API readsMetafields, markets, translations, inventory: one passthrough tool, with Shopify's own cost figures returned so the model paces itself.
• Reporting where you workSummarize the week's orders in the client you already have open, without exporting customer data into a spreadsheet first.

• The scopes you granted the BoostEcom app decide what succeeds, and Shopify enforces them on every query
• Shopify's own cost and throttle figures come back with the data, so the model paces itself
• A mutation sent through it is refused like any other write

tools/call shopifyAdminGraphQL

query {
  markets(first: 5) { nodes { name handle } }
  shop { metafields(first: 5) { nodes { key value } } }
}

{
  "data": { "markets": { … }, "shop": { … } },
  "cost": { "requestedQueryCost": <n>, "actualQueryCost": <n> },
  "throttleStatus": {
    "maximumAvailable": <n>,
    "currentlyAvailable": <n>,
    "restoreRate": <n>
  }
}

1. 1

   Connect the store

   Create your account and install the BoostEcom app from your Shopify admin, in one click. The access you choose in the app caps everything that follows.

   Shopify grants that open tools

   • read_products
   • read_orders
   • read_content
   • read_themes
   • read_analytics
   • read_reports
2. 2

   Paste the URL in your client

   Claude and ChatGPT take it as a custom connector. Claude Code and Cursor take it in their config, then open the same consent screen.

   The URL to pasteurl

   https://www.boostecom.app/api/mcp/v1/<STORE_ID>

   Copy
3. 3

   Approve the scopes

   The consent screen names each permission in plain words and offers only what you granted the BoostEcom app.

   What your client asks forhttp

   GET https://www.boostecom.app/oauth/authorize
     ?response_type=code&client_id=<CLIENT_ID>
     &resource=https://www.boostecom.app/api/mcp/v1/<STORE_ID>
     &scope=boostecom:store.read boostecom:catalog.read
     &code_challenge=<S256>&code_challenge_method=S256

   Copy
4. 4

   Ask about your store

   Your client lists the tools your grant opened and calls them whenever a question needs live data.

   What your client can list

   • getStoreContext
   • getShopInfo
   • runAudit
   • listProducts
   • getProduct
   • listOrders
   • listPages
   • getMetafields
   • listMetaobjectDefinitions
   • listMetaobjects
   • listThemes
   • getTheme
   • runShopifyQL
   • introspectSchema
   • shopifyAdminGraphQL
   • getStudioSection
   • getStudioProduction
   • listStudioGenerations
   • getStudioPricing
   • getStoreIntelligence
   • listThemeUpdates
   • getUpdateJob
   • listBackups
   • getUptime
   • getAppEmbedStatus
   • getDomainHealth
   • getActionRequest
   • searchDocs
   • getDoc
   • helmListModels
   • helmPlanSection

Tokens issued before this catalog existed carry the legacy mcp grant. It keeps the Shopify read tools it already had and never opens a BoostEcom system: Studio, store intelligence and the docs tools need a scope approved on the consent screen.

• No account, no key: 60 calls a minute per IP
• A bei_ key raises it to 6,000 a minute, per organization
• Public records only

{
  "mcpServers": {
    "boostecom-intelligence": {
      "url": "https://www.boostecom.app/api/mcp/intelligence"
    }
  }
}

curl -s https://www.boostecom.app/api/mcp/intelligence/manifest

See what Intelligence reads

Measured on a store connected through a merchant's Custom App: a store that grants fewer scopes gets fewer. With the BoostEcom app, the ceiling is what you grant the app.

Custom plans run uncapped. A refused call names the plan, the limit it hit and what to do next.

• It does not write. Every mutation is refused and logged. A change to your store goes through the dashboard, where you approve it.
• It stays inside what you granted the app. A tool your Shopify grant cannot satisfy is never registered, so your client never sees it.
• A static key stops at 15 tools. A key names a store, never a person. Studio, store intelligence, the BoostEcom app's records and the docs tools need an OAuth sign-in.
• One request, 30 seconds. A tool call that runs longer is cut off. Long work belongs in a dashboard workflow, not in a tool call.
• No API or SDK of our own. The supported surfaces are this endpoint, the Intelligence MCP server and the Intelligence REST API. The GraphQL you reach is Shopify's, through the passthrough.