Shopify MCP Server: What Dev MCP and Storefront MCP Do

Yes, Shopify has an MCP server, in fact several. MCP (Model Context Protocol) is an open protocol that lets an AI assistant connect to external tools and data. Shopify publishes more than one official "Shopify MCP server", and each one serves a different audience. Many guides blur them together, and some are out of date.

This article separates them, gives the URLs and tools that Shopify documents, and flags what has changed. Details move quickly here, so confirm anything you plan to build on in the Shopify docs.

Does Shopify have an MCP server?

Shopify offers these official MCP surfaces:

1. Dev MCP (also called Shopify.dev MCP, package @shopify/dev-mcp): for developers and coding assistants.
2. Storefront MCP and its replacement, UCP-compliant catalog, cart and checkout servers: for shopping agents that interact with a store.
3. Customer Accounts MCP: for authenticated, customer-specific actions.

One gap matters for merchants. In the research behind this article, no official Shopify MCP server for authenticated Admin store writes (editing products, changing prices, fulfilling orders) turned up. Third-party guides say community-built servers fill that gap. Treat those as unofficial and check them carefully before connecting them to a live store.

What is Shopify Dev MCP?

Shopify Dev MCP is a local server that gives an AI coding assistant access to Shopify's developer resources. It can search documentation, introspect API schemas (read the list of fields and operations an API supports), and answer questions about Shopify APIs using current information rather than whatever the model remembered from training.

Key facts from Shopify's docs and changelog:

• It runs on your machine and does not require authentication.
• The install command is npx -y @shopify/dev-mcp@latest. The same command is used across MCP clients, though the config file format differs per client.
• On 2025-10-01 Shopify expanded code generation support to the Storefront API, Partner API, Customer Account API, Payment Apps API, Polaris Web Components and Liquid.
• Shopify now presents it as one install option inside the Shopify AI Toolkit, "if you prefer MCP".

Shopify Dev MCP tools

Early versions exposed search_dev_docs and introspect_admin_schema. A third-party listing also names fetch_docs_by_path. Tool names can change between releases, so check your client's tool list after installing rather than relying on a blog post. Optional Liquid (theme template language) validation is reported to be switched on through environment flags, but that detail comes from a community README, so check the official repository.

What Dev MCP cannot do

It does not read or change live store data. It works against documentation, schemas and your local code. If a guide says it lets you "execute store operations through natural language", that conflicts with Shopify's own description and should be treated as unverified.

Who it is for: agencies and developers building apps, themes and custom storefronts. Merchants who never write code have little reason to install it.

What is Storefront MCP, and why do older guides get it wrong?

Storefront MCP is a hosted endpoint on each store, not something you install. Early guides describe it as https://{shop}/api/mcp, with no authentication, offering catalog search and cart tools.

That description is now outdated. According to Shopify's Storefront MCP page, the catalog and cart tools on /api/mcp were removed, and Shopify points developers to the Universal Commerce Protocol (UCP) instead. The migration map on that page:

Old tool on /api/mcp	Replacement
search_catalog, get_product_details	Storefront Catalog MCP: search_catalog, lookup_catalog, get_product
get_cart, update_cart	Cart MCP: create_cart, get_cart, update_cart, cancel_cart
Checkout URL from the cart	Checkout MCP

A third-party summary says search_shop_policies_and_faqs remains on /api/mcp and needs no authentication. Verify that against the current Shopify page. The same summary says the sample shop-chat-agent app is deprecated.

The timeline in guides varies. Shopify announced that Storefront Catalog MCP implements UCP around April 2026, and one source says the old search and lookup tools were scheduled for removal on June 15, 2026. A claim that old cart tools remain until August 31, 2026 is unconfirmed, and the official page already describes them as removed. If you built on the old tools, assume they no longer work.

What are the UCP catalog, cart and checkout servers?

UCP (Universal Commerce Protocol) was announced by Google with Shopify for agentic shopping and checkout. It is a commerce protocol, which is different from MCP: MCP connects an assistant to tools and data, while UCP defines how agents browse, build carts and check out. Shopify's UCP-compliant servers are delivered over MCP.

Shopify MCP server URL options

These are the endpoints Shopify documents for the catalog:

• Global Catalog, which searches across Shopify merchants: https://catalog.shopify.com/api/ucp/mcp
• Storefront Catalog, scoped to one merchant: https://{storeDomain}/api/ucp/mcp

Both use an agent profile and need no API key. Replace {storeDomain} with the store's domain. Confirm current URLs in the Shopify agents docs before use, since this area is still changing.

Cart MCP, Checkout MCP and Checkout WebMCP

• Cart MCP builds and updates carts with line items, localization and buyer context.
• Checkout MCP creates and manages a checkout session from your own server. Its tools require authentication or a signed request. Shopify recommends it unless your agent has to run in the buyer's browser.
• Checkout WebMCP reads and updates the buyer's current checkout and places the order from the buyer's browser. TechCrunch reported on 2026-09-28 that Shopify launched WebMCP support for checkout, including Shop Pay, for eligible merchants.

Some third-party pages still say Checkout MCP is "in preview for select partners only". Shopify's current docs describe it as a recommended, documented path, so do not rely on the preview claim without a fresh official source.

What does Customer Accounts MCP do?

Customer Accounts MCP provides tools for customer-specific actions such as order management and account details. It is meant for authenticated requests, for example checking an order's status or managing account preferences.

Its endpoint is not a fixed URL. It is discovered dynamically from the shop's storefront domain through a discovery endpoint. Shopify's page also notes that catalog, cart and checkout tools are now documented under its agentic commerce section.

How do the Shopify MCP servers compare?

	Dev MCP	Storefront / UCP MCP	Customer Accounts MCP
Audience	Developers and coding assistants	Shopping agents	Authenticated buyers via an agent
Runs	Locally on your machine	Hosted by Shopify, per store	Hosted, discovered per shop
Authentication	None	None for catalog and policies; auth or signed requests for Checkout	Customer authentication
Store data	No	Yes (catalog, cart, checkout)	Yes (orders, account)
Typical use	Build apps and themes with accurate docs	Let an agent find products and buy	Order status, account tasks

Which one should a merchant or agency use?

• Building or maintaining a store, app or theme: install Dev MCP in your coding assistant. It carries no store risk because it never touches live data.
• Preparing for AI shopping agents: read Shopify's agents documentation on UCP and decide whether your storefront needs custom agent work. Much of this is infrastructure Shopify hosts for you.
• Wanting an assistant to analyze or edit your own store: none of the official servers above are built for that. For how assistants read catalog data, see Shopify MCP Explained: How AI Assistants Read Your Catalog. For connecting Claude to a store, see Connect Claude to Shopify: The Complete Step-by-Step Guide.

Is it safe, and what can go wrong?

Start read-only. Dev MCP is the lowest risk because it only reads docs and schemas. The catalog servers are public and unauthenticated, which means they expose what a shopper could already see. Checkout and customer account tools involve money and personal data, so use authentication and test on a development store first.

Common problems:

• Following outdated guides. Many 2026 posts still describe catalog and cart on /api/mcp. Check the date and compare with Shopify's docs.
• Mixing up the servers. Dev MCP cannot answer questions about your sales, and the catalog servers cannot edit your products.
• Unverified claims. Statistics about stores discoverable in AI assistants, or claims that servers are live by default on every store, had no official source in the research for this article. Ask for a Shopify source before repeating them.
• Community Admin servers. If you use one, give it the narrowest access scope available, and prefer read-only tokens.
• Unknowns. Rate limits, pricing and exact availability dates were not verified. Check the vendor docs.