MCP overview

What the shop MCP server is, how it's architected, and why any agent benefits.

The shop MCP server exposes this platform to AI agents over the Model Context Protocol. An agent connected to it can build and operate a store end-to-end: products, themes, sections, pages, content, translations, and more.

What it provides

• Tools — ~50 typed operations over the GraphQL API (create products, build sections, set the palette, publish themes, upload images…). See the tools reference.
• Skills — reusable playbooks (e.g. shop-builder) that encode how to build correctly. They're served over the protocol, so any client benefits just by connecting.
• Instructions / prompts / resources — a skill catalog rides in the initialize response; skills are also skill:// resources and skill_<name> prompts.

Architecture

• One org = one store. Each connection resolves its organization, store, and active theme from the API key — no need to pass IDs on every call.
• Two transports:
  • stdio — the client launches the local shop-mcp binary; the key + context come from environment variables.
  • streamable HTTP — a hosted endpoint at /mcp; each request carries its own Authorization: Bearer crmk_…, and the per-key server is built once and cached.
• Self-hosting & safety — write tools re-host foreign image URLs, enforce the theme design contract, and respect org isolation just like the API.

Authentication

Use an organization API key (crmk_) with the scopes your work needs (products:write, webstore:write, settings:write).

Next

• Connect — config for Claude Code, Cursor, Claude Desktop, VS Code.
• Tools reference · Skills