MCP for Ecommerce: Connect Claude to Shopify and Klaviyo

Here's my hot take. The most useful AI upgrade for a Shopify founder this year isn't a new model. It's a cable.

MCP ecommerce, in plain words: the Model Context Protocol lets Claude plug into your Shopify store and your Klaviyo account, read the real data, and take actions you approve. Shopify's official route is the Shopify connector for Claude, which works with products, collections, inventory, orders, customers, discounts and analytics. Klaviyo's MCP server gives Claude over 260 tools across campaigns, flows, segments and reports. Both install from inside Claude with an approval screen. Start read-only.

That's the answer. The rest of this post is which server does what, what each one is blocked from doing, and the one place MCP can't help you at all.

What is MCP, and why should an ecommerce founder care?

The official MCP site calls it "an open-source standard for connecting AI applications to external systems," and compares it to a USB-C port. One plug shape. Any tool that speaks it can connect to any AI that speaks it.

Before MCP, using Claude on your store meant exporting a CSV, pasting it in, and hoping you grabbed the right columns. Claude could think about your business. It couldn't touch it.

Now it can. Ask "which flows made the most money last month" and Claude calls Klaviyo's flow report tool, reads the numbers, and answers with your data. Ask "how many Vanilla Bean Candles are left" and it checks inventory in your Shopify store.

Your AI stops guessing about your store the day it can read your store.

Which Shopify MCP do you actually need?

This is where most guides go wrong, because "Shopify MCP" now means five different things, and most of them aren't for you.

Shopify's old Storefront MCP catalog and cart tools were removed. Shopify's migration page says they moved to the Universal Commerce Protocol at a new endpoint, built for shopping agents. If you read a 2025 tutorial telling you to point Claude at /api/mcp to manage your products, it's stale. (The standards behind that shift are covered in Agentic Commerce Protocol vs Universal Commerce Protocol.)

Here's the current map, from the vendors' own docs:

MCP option	Built for	What it can do	What it can't do
Shopify connector for Claude	Store owners	Products, collections, inventory counts, percent-off discount codes, read orders and customers, analytics questions	Refunds, cancels, returns, gift cards, your live theme, payments, taxes, domains
Klaviyo MCP server	Marketers with an Owner, Admin or Manager role	Over 260 tools: campaign and flow reports, segments, flows, campaigns, templates, profiles	Anything outside your Klaviyo account; local setup needs your own API key
Shopify AI Toolkit and Dev MCP	Developers	Search Shopify docs and API schemas, validate GraphQL and Liquid	Read your store's sales data (the Dev MCP needs no store login at all)
UCP Storefront Catalog, Cart and Checkout MCP	Shopping agents and app builders	Search a store's catalog, build carts, hand off to checkout	Run your back office
Customer Accounts MCP	Apps serving logged-in shoppers	Order status, order details, account preferences	Work without a custom domain and OAuth setup

So for running your store, you want row one. Shopify's Claude connector page lists every action it takes by name: list-orders, create-product, set-inventory, create-discount, run-analytics-query, and a few dozen more. That last one runs a ShopifyQL query, so you can ask "What's my average order value this month compared to last month?" and get a table back.

And skip the GitHub repo promising a "Shopify MCP" with your admin token pasted in. Shopify's authorization page says to use the official integration and not to create an API access token or build your own integration to connect an AI tool to your store.

If you're a developer, the Shopify AI Toolkit is your row. It installs as a Claude Code plugin, and the Dev MCP server still works if you'd rather add it by hand. Building an AI assistant for your shoppers? That's the Customer Accounts MCP plus UCP, and a different post. Selling to other people's AI agents instead is covered in Shopify agentic storefronts.

What can Claude do inside Klaviyo through MCP?

A lot more than read reports. That's the part founders underestimate.

Klaviyo's available tools page lists over 260 tools. The ones that matter for a Shopify brand:

• Reporting: get_flow_report and get_campaign_report, plus query_metric_aggregates for raw event data like Placed Order.
• Segments: get_segments, create_segment, update_segment, and query_segment_series to watch a segment grow or shrink over time.
• Flows: get_flows, create_flow, and update_flow, which changes a flow's status.
• Campaigns: create_campaign, assign_template_to_campaign_message, and yes, send_campaign.
• Templates: create_email_template, render_email_template, and drag-and-drop template tools.

Read that list again. Claude can build a segment, write a flow, and send a campaign to your whole list. On the same afternoon.

That's why I'd never connect it with full write access on day one. Klaviyo gives you the brake: add read-only=true to the server URL and every tool that can change your account switches off. You only get query parameters with a custom connector, though. The one-click listed connector in Claude doesn't take them.

My take: let Claude read and recommend for two weeks. A good first job is auditing your post-purchase flow against these Klaviyo post-purchase flow examples. Then give it write access to build things as drafts you review in Klaviyo. Never let it send.

An AI with send access to 40,000 inboxes is a faster mouth. Make sure it's saying something worth hearing.

If you'd rather stay inside Klaviyo's own interface, its built-in assistant does similar segment and flow drafting. I compared the two approaches in my Klaviyo Composer review.

How do you connect Claude to Shopify and Klaviyo safely?

Both installs start in Claude. Neither is on the Shopify App Store.

Shopify: In Claude, open the Shopify connector install page. You get redirected to your Shopify admin to approve a data access level. Read-only lets Claude view data. Write access lets it edit. One catch from Shopify's docs: you can't lower an access level you already approved. To shrink it, uninstall and reinstall.

Klaviyo: In Claude, open Settings, then Connectors, search for Klaviyo, connect, and click Allow. For the read-only brake, use Add custom connector instead with the URL https://mcp.klaviyo.com/mcp?read-only=true. Klaviyo's connection guide has both paths.

Now the guardrails Shopify built in for you. Per its considerations page, a connected AI tool can't issue refunds, cancel or capture orders, process returns, touch gift cards, edit or publish your live theme, or change payments, taxes or domains. Even with write access. It can edit an unpublished theme copy, and it changes items one at a time, so a big batch can stop halfway.

Klaviyo flags a sneakier risk. Some tools read user-generated content, like reviews and profile properties. A customer could type instructions into a review, and your AI could read them as commands. Klaviyo's fix is a second parameter, disable-tools-with-user-generated-content=true. I'd turn it on.

One more habit: in each new chat, keep only the connector you need turned on. Klaviyo recommends it too.

What should you ask Claude first?

Start with questions that would take you 40 minutes of clicking. Here are five I'd run on day one:

1. "Show me my total sales for the last 30 days, broken down by product." (Shopify)
2. "Which of my flows made the most revenue last month, and which made the least?" (Klaviyo)
3. "How big is my segment of customers who ordered once and haven't ordered in 90 days?" (Klaviyo)
4. "Show my top-spending customers." (Shopify)
5. "Which product shows up most in first orders?" (Shopify)

Then put two answers side by side, which is where the cable pays off.

Run the math on a store like this, a hypothetical. Claude finds 4,200 customers who bought once and went quiet for 90 days. It drafts a winback segment and a three-email flow. If 3% come back at a $62 average order value, that's 126 orders and $7,812. Not bad for a chat.

But here's the thing. Every one of those 126 people clicks an email and lands on a product page. Same page that didn't convince them to reorder the first time.

Where does MCP stop helping?

At the page. MCP connects Claude to your tools. It doesn't make your product page close.

I've watched founders spend a weekend wiring AI into every tool they own while their hero product page still reads like a spec sheet. That's amplifying a leak. Faster segments, smarter flows, more clicks, all landing on a page that converts 1 in 100.

Here's what fixing the page did for one product. A bedding brand's Adjustable Pillows page went from a conversion rate of 1.0% and an average order value of $125 to 4.4% and $152. Revenue per visitor went from $1.25 to $6.68. On 10,000 visitors, that's $12,500 before and $66,800 after. See the full case study numbers. Real client numbers, not typical results, and not a promise of what your store will do.

Before the page rebuild $12,500

After the page rebuild $66,800

Real client result from /results. Revenue per visitor x 10,000 visitors. Not typical, not a promise.

No new segment did that. No new flow. The page did.

MCP makes your marketing faster. Only the page makes it pay.

So use MCP to find the leak. Ask Claude which product gets the most traffic and the lowest conversion. Then fix that page first. Our guide to revenue per visitor shows how to score every product on one number, and the Klaviyo flows for Shopify guide covers the seven flows worth pointing at it.

Frequently asked questions

What is MCP in ecommerce? An open standard that lets Claude connect to Shopify, Klaviyo and other tools, read your real data, and take actions you approve.

Is there an official Shopify MCP for store owners? Yes, the Shopify connector for Claude. The developer MCP servers are for builders and shopping agents, not for running your store.

What can the Klaviyo MCP server do? Over 260 tools: reports, segments, flows, campaigns, templates. It can even send a campaign, so start read-only.

Can Claude refund orders or change my live theme through MCP? No. Shopify blocks refunds, cancels, returns, live theme edits, and payment, tax and domain changes.

Is it safe to connect Claude to Klaviyo and Shopify? As safe as the access you approve. Start read-only and switch off tools that read reviews and profile text.

What to do next

Connect Klaviyo to Claude today with read-only=true on the URL. Ask one question: "Which of my flows made the most revenue last month, and which product page do those emails send people to?" Then open that product page and read it like a stranger would.

For the full map of AI channels and tools, start with our AI commerce guide.

---

Book Your Profit Audit

MCP can find the product where your traffic is bleeding out, but it can't rewrite the page that's doing the bleeding. Get your free profit audit and we'll show you the exact leak, then show you how to rebuild a high-converting product sales page in less than 15 minutes.

Book Your Profit Audit →

Or go here to check it out → revenueflows.ai

P.S. Plugging Claude into a leaky page just finds the leak faster. Plug it into a page that closes and every flow you build starts printing.