Store platform

Shopify Customer Account MCP

Shopify's Customer Account MCP lets an agent act for a signed-in customer: look up their orders, account details and subscriptions through an authenticated, per-customer connection.

What it is and why it matters

What it does

• Authenticate a customer and act within their account scope
• Look up order history and status for the signed-in customer
• Work alongside Storefront MCP for a logged-in shopping flow
• Keep customer data access tied to the customer's own authorization

Best for

Developers building shopping or support agents that need to act for an authenticated customer on a Shopify store.

How to connect it

1. Confirm the requirements described in the documentation: the store has a custom domain, your app meets Shopify's protected customer data requirements, and the app is set up for customer accounts authentication.
2. Scaffold an app with Shopify CLI (or link an existing Dev Dashboard app using the command in the documentation) and create a dev store with sample products for testing.
3. In the Dev Dashboard, open API access requests and request Protected customer data access. Give a clear reason for it and for each field you select (name, email, phone, address).
4. Add the access scopes and customer authentication redirect URIs to your app configuration file, as shown in the documentation, using your real app domain.
5. Deploy the app and install it on the dev store. Then discover the MCP endpoint and OAuth endpoints from the store's storefront domain, as described in the documentation.
6. Implement the authorization code flow with PKCE to get an access token, send MCP requests with that token, and use the tools/list command to see which tools are available. Test only on the dev store first.

Exact commands and addresses change. Use the official documentation for the current steps.

Installation guide for Shopify Customer Account MCP

Client-by-client steps, what to prepare, the first prompts to run and fixes for common errors.

ClaudeChatGPTGeminiMicrosoft CopilotPerplexityCursorClaude Code

→

Questions you can ask it

• Look up the status of order #1042 for the signed-in customer.
• Show me the details of my most recent order, including items and totals.
• What account details do you have on file for me?
• List the tools this server offers and what each one needs as input.

What it cannot do

• It cannot be used without a customer signing in. Every request depends on that customer's own access token, so it cannot look across all customers.
• It is not a plug-and-play connector for non-technical users. The documentation describes app configuration, OAuth with PKCE and code, so developer work is required.
• It does not cover catalog, cart or checkout. The documentation points to separate Storefront Catalog, Cart and Checkout MCP tools for those.

Staying safe

• This server handles personal customer data. Only request the protected customer data fields you need and give accurate reasons for each, as the documentation requires.
• Store access tokens securely and keep each token tied to the customer who authorized it. Never share tokens between customers or sessions.
• Because access varies by tool, check each tool's schema with tools/list. Start with read-only lookups such as order status, and enable anything that changes account preferences only after supervised testing on a dev store.

Watch out for: Involves customer authentication and personal data. Review the authorization flow and what the agent is allowed to do before enabling it.

Frequently asked questions