How do I enable Shopify MCP servers for my store?

Shopify Plus merchants enable the four native MCP servers (Storefront, Customer Account, Checkout, Dev) from Settings → Apps and sales channels → MCP. Toggle each server on, scope its permissions, and copy the endpoint URL into your AI client (Claude Desktop, Cursor, Continue, etc.). Verify the connection by asking the agent to query a product or list orders — if you get a structured response, the connection is live.

What does a custom Shopify MCP server cost to build?

Realistic 2026 ranges: £8,000 to £25,000 for a single-tool custom MCP server (loyalty balance lookup, custom B2B catalogue, ERP-backed inventory query). £25,000 to £80,000 for a multi-tool production server with authentication, multi-tenancy, observability, and rate-limit handling. Above that range, you’re typically wrapping a non-trivial backend rather than building MCP from scratch.

When should I build a custom MCP server vs. using Shopify’s native ones?

Use Shopify’s native servers whenever they cover your use case — they’re free, maintained by Shopify, and update with the platform. Build custom only when you need to expose data or actions that the native servers do not: loyalty balances, custom B2B price lists, ERP-backed inventory, gift card lookups, custom app data. Most merchants we audit start with the native servers and add a single custom server if a specific gap surfaces.

Shopify MCP Server: Production Implementation Guide (2026)

Shopify shipped MCP (Model Context Protocol) support across four separate servers during Q1 2026 — Storefront, Customer Account, Checkout, and Dev. For merchants on Shopify Plus the Storefront + Customer Account + Checkout servers are managed infrastructure: Shopify runs them, you enable them. For agencies and in-house teams, the Dev MCP is the one that matters day to day. This guide covers both.

What Each Shopify MCP Server Actually Exposes

The Four Servers

Storefront MCP — Unauthenticated product discovery. Search, variants, collections, pricing, inventory availability, media. Intended for any AI agent that wants to recommend your products.
Customer Account MCP — Authenticated customer actions. Order history, tracking, saved addresses, loyalty balance, subscription management. OAuth'd per customer.
Checkout MCP — Cart and checkout operations. Add/remove line items, apply discounts, calculate shipping and tax, finalise order. Powers ACP-style checkout on behalf of the buyer.
Dev MCP — For developers. Access to Shopify documentation, CLI commands, code generation, and debugging helpers from inside Claude Desktop, Cursor, Windsurf, or any MCP-aware IDE.

Enabling the Managed Servers

Per the Shopify developer documentation, every Shopify store has its own Storefront MCP endpoint exposed at https://{storedomain}/api/mcp (or https://{storedomain}/api/ucp/mcp following the UCP migration on April 22, 2026). The endpoint accepts JSON-RPC 2.0 POST requests and currently requires no authentication for the catalog and policy tools. You do not deploy anything — Shopify runs the infrastructure.

Customer Account and Checkout MCP cover authenticated commerce flows. Per the Shopify agents docs, Checkout MCP exposes tools like create_checkout, update_checkout, and complete_checkout at the same UCP-aligned endpoint, and authenticated calls require a Bearer token associated with the agent profile. Customer Account MCP follows the same pattern for authenticated customer actions. These are not simple admin-toggles in production — your agent has to acquire and rotate the right credentials per merchant.

Verifying the Storefront MCP Works

Connect Claude Desktop to your Storefront MCP as a test:

Claude Desktop → Settings → Developer → Edit Config.
Add a server entry pointing to https://{storedomain}/api/mcp (or /api/ucp/mcp for UCP).
Restart Claude Desktop.
In a new chat: "Search this store for <product category you sell> and show me three matching products with prices."

If the agent returns structured results with images, variants, and correct pricing, your endpoint is healthy. If it returns nothing or wrong data, the issue is almost always product data completeness — metafields, product types, vendor tags, or availability. Fix the catalogue before blaming the protocol.

Using the Dev MCP

Dev MCP is genuinely useful if your team builds on Shopify. Once the Shopify Dev MCP server is configured against your IDE — Cursor, Claude Code, Windsurf, or any MCP-aware client — the agent gains access to the latest Shopify CLI commands, Admin GraphQL schema, Polaris component docs, Storefront API reference, and Function examples. Treat the Shopify Dev Assistant docs as the source of truth for the current install path; the configuration moved between Shopify product surfaces in early 2026 as the AI Toolkit landed. For an agency like ours it replaces three tabs of docs that we used to have open constantly.

Anchor Loyalty (our Shopify loyalty app) is now developed with Claude Code + Dev MCP running in the background. Any time a developer asks "how does this GraphQL mutation work?", the agent pulls the live schema rather than a stale Stack Overflow thread.

When a Custom MCP Server Makes Sense

For most merchants: never. Shopify's managed MCP coverage is already broader than what an in-house team would build in six months. The exceptions we have seen:

Deep ERP integration — A custom MCP server exposing NetSuite or SAP inventory alongside Shopify, so an agent can answer "when will this back-ordered item ship?"
Private B2B catalogues — Account-specific pricing and product availability that should never hit public channels. Host behind authentication, expose over a private MCP endpoint, agent requires a per-account token.
Custom fulfilment workflows — Warehouses with their own inventory logic, subscription engines with complex modification rules, or marketplaces with seller-specific pricing.

Cost of a Custom MCP Server

Our going rate for a production-grade custom MCP server in Q2 2026 is £15,000-£45,000 depending on scope. That covers the server implementation itself, authentication, observability, test coverage, and deployment. Add another £5,000-£15,000 if the underlying data source does not already have a clean API. See our full custom app cost breakdown for how we structure the quote.

Security and Rate Limiting

Every MCP request we see in production carries an X-MCP-User-Id or equivalent agent identifier. Treat these exactly like any other client: authenticate, rate-limit, log. Shopify's managed endpoints handle this for you. Custom servers must implement it themselves — we default to 60 requests/minute per agent identifier, plus global burst limits, plus structured audit logging of every tool call the agent made.

What to Expect Next

Shopify has committed to shipping the remaining MCP servers (Fulfilment, Analytics) in 2026. BigCommerce, Commercetools, and SFCC have all signalled MCP support on their 2026 roadmaps. Our advice for merchants: get the Shopify managed servers working cleanly first. Do not pre-build against standards that are still negotiating their v1.

Going deeper on agentic commerce: what GPT-5.5 means for Shopify agentic commerce, how ACP, MCP, and UCP fit together, scaling MCP in production, production patterns for Shopify Functions, and optimising for ChatGPT and Perplexity Shopping.