How Does Claude Build a Shopify Page in PageFly?

Updated September 29, 2026: added a 45-second demo of the connector, and how to use the same PageFly MCP server in ChatGPT and other AI assistants.

Merchants have started asking AI assistants to do the store work, not describe it. In the three months to 9 September 2026, PageFly's own Google Search Console recorded merchants landing on pagefly.io from queries like how to link claude to shopify — a question that, until this month, had no real answer.

It has one now. Since September 2026, PageFly — a Shopify page builder behind 320+ page and section templates, rated 4.9 from nearly 5,900 Shopify App Store reviews and carrying Shopify's Built for Shopify badge — is listed in the Claude Directory as a community connector. Connect it once and Claude can open the PageFly pages on your store, write new sections in PageFly's own element vocabulary, change the sections that are already there element by element, preview everything inside your live theme, and publish when you say so.

That is a different thing from an AI that gives you advice about your pages. The slow part of shipping a Shopify landing page was never the typing — it was the round trip between deciding what the page should say and getting it built. Your page builder now takes a brief, not a click path. You still approve every publish.

What is the PageFly connector for Claude?

The PageFly connector for Claude is a Model Context Protocol (MCP) server, published in the Claude Directory since September 2026, that gives Claude a set of 23 tools for reading, building, editing, previewing and publishing PageFly pages on one Shopify store you have approved. Its connector URL is https://apps.pagefly.io/mcp, it is labelled a community connector, and it requires sign-in.

MCP is the open standard assistants use to reach an outside system. That is why the same connector works in Claude and in other MCP-compatible clients rather than being a Claude-only feature — the same shift that put storefronts inside AI conversations in the first place, which we covered in our guide to Shopify agentic commerce.

What this is not

It is not a chatbot bolted onto the PageFly editor, and it is not a code generator. Claude writes in PageFly's native element vocabulary, so what it produces is a real PageFly page you can open and keep editing by hand — not exported markup you inherit and maintain. If you have been weighing prompt-to-store tools, that distinction is the whole argument in vibe coding vs PageFly.

What changed after launch

The connector shipped in early September able to append and little else, which meant one bad section cost you a whole new page. That is no longer true. Since 12 September the connector reads a section the way PageFly's own editor reads it — every element by its address, its copy, its settings and its style per breakpoint — and applies a set of changes to it in place. Anything your instructions do not name is kept.

Two details are worth knowing because they change how much you can trust it:

• An edit costs no AI credits. No model runs on PageFly's side for a section edit. Your assistant proposes the change; PageFly checks it, applies it and reports back on what actually landed.
• A refused change refuses the whole set. If one instruction in a batch cannot be applied safely, nothing is applied, and Claude is told what the check objected to. You never end up with half an edit and no way to know which half.
• Your own editor saves win. Every write carries the version the page was read at. If you saved that page in the PageFly editor between Claude reading it and Claude writing, the write is refused instead of overwriting your work.

What Claude can actually do with your pages

Five prompts you can paste as-is once the connector is on. Each one names the tools that run behind it, because the tool list is the honest boundary of what the connector can do.

1. Build a Black Friday landing page from three products

What runs: get_page_authoring_guide, search_templates, list_shop_media, create_page, add_section, preview_page. What you get: an unpublished PageFly page, assembled section by section (up to 10), using your own uploaded media and product photos, with a preview link after each section so you can redirect mid-build. If you are timing this for the season, our Shopify BFCM checklist sets the deadlines.

2. Change one headline on a page you built yourself

What runs: get_page, get_section, apply_section_edit, preview_page. What you get: that headline changed, in place, on a page Claude never touched before — your spacing, your styles, your product bindings all left alone. This is the part merchants ask about most, so it is worth being exact: the assistant is not re-authoring your section from a summary of it. It reads the real element tree, proposes named operations against specific elements, and PageFly applies them. If you want the whole section replaced instead, update_section does that; move_section reorders, delete_section removes, and update_page renames a page or changes the handle its URL is built from.

3. Ask why a page is converting badly

What runs: get_page, get_page_health, get_cro_findings. What you get: the actual findings from your store — broken links, missing images, the conversion issues surfaced by AI Page Checkup — rather than generic advice. Claude will say it has no data if you have not run a scan yet, which is the correct answer. Now that it can also edit the page, "why is this weak" and "fix it" are one conversation rather than two jobs. The reasoning behind those findings is in our CRO work.

4. Read an A/B test result and decide the next move

What runs: get_ab_test_results. What you get: the status and outcome of tests you ran with PageFly A/B testing, in the same conversation where you can act on them. This is the step most merchants skip: a finished test that nobody reads is a test that cost you traffic for nothing.

5. Find a template, preview it, then publish

What runs: search_templates, add_section, preview_page, publish_page. What you get: a search across our 320+ page and section templates, a section added where you want it rather than only at the bottom, a preview rendered inside your live theme, and a storefront change only after you ask for it. Publishing uses your plan's live-page allowance, not AI credits — the allowance for each tier is on PageFly pricing.

How to connect PageFly to Claude

Three things before you start: PageFly installed on the store (any current plan, Free included), a Claude account on any plan, and the ability to approve an app connection in that store's Shopify admin.

1. Search the Claude Directory. Open the Claude Directory, search pagefly, and click the PageFly result.
2. Open the listing and connect. The listing shows the connector URL, who made it, and every tool it exposes. Read the tool list — it is the real contract. Then choose Connect to Claude.

3. Enter your store name. Just the handle — my-store for my-store.myshopify.com.
4. Approve access in your Shopify admin. This is the permission step, and it happens in your admin, not in Claude.
5. Go back to Claude and ask it something small. "List my PageFly pages" is the fastest way to confirm the connection is live.

Two gotchas worth knowing before they bite. The setup link expires after 15 minutes, so if you walk away mid-connect you start again from the assistant. And in Claude Code the whole thing is one line: claude mcp add --transport http pagefly https://apps.pagefly.io/mcp. Full requirements, per-assistant setup and troubleshooting are in the AI Assistant Connector documentation, alongside PageFly's other integrations.

Use the PageFly MCP server in ChatGPT and other assistants

The Claude Directory listing is one way in, not the product. Underneath it, PageFly runs a remote MCP server at https://apps.pagefly.io/mcp. Any assistant that can add a remote MCP server with OAuth sign-in gets the same tools, the same one-store approval in your Shopify admin, and the same rule that nothing is published until you say so. You are choosing a chat window, not a different PageFly.

Connect PageFly to ChatGPT

ChatGPT adds custom MCP servers through Developer mode, which is available on paid plans: Plus, Pro, Business and Enterprise. The Free plan cannot add them.

1. Turn on Developer mode. In ChatGPT, open Settings → Apps → Advanced settings and enable Developer mode.
2. Add a new MCP server. Name it PageFly and paste the connector URL https://apps.pagefly.io/mcp.
3. Enter your store name and approve. Type the store handle, then approve the connection in your Shopify admin. The approval link expires after 15 minutes.
4. Ask it something small. "List my PageFly pages" confirms the connection. Every prompt in this guide then works the same way in ChatGPT.

Cursor, VS Code and other MCP clients

Clients that support remote MCP servers with OAuth take the same URL: add https://apps.pagefly.io/mcp as a server, then approve the connection in your Shopify admin. You can also copy the URL from PageFly's settings.

On the PageFly side nothing changes between assistants: every current PageFly plan, Free included, gets the full connector, and publishing uses your plan's live-page allowance. The setup guide walks through each client.

From a landing-page idea to a live PageFly page

The five prompts above each start with you already knowing what the page should say. Most campaigns do not start there. Here is the longer path, from a blank page to a built one, with the design settled before anything is built on your store — and it starts by admitting that a campaign page has one job, which is not the job your homepage does.

1. Argue the angle out in Claude first. Ask for five angles for the campaign, then say which customer objection each one answers. The one that survives that question is your page. Our guide to building a Shopify landing page that converts is the checklist to argue against, and the Shopify landing page examples are angles that already earn their traffic.
2. Draw it before you build it. Hand the winning angle to Claude Design, Anthropic's visual tool for Pro, Max, Team and Enterprise accounts, and ask for the page as a design — desktop and mobile side by side, because the phone version is the one most of your traffic will see. You are looking for section order and hierarchy, not final pixels. Move things around until the page argues in the right order.

3. Turn the design into a section list. Ask Claude to read its own design back as an ordered list of sections, one line each, naming the products and images that belong in them. That list is the brief. It is short, it is checkable, and it is the thing you will correct — correcting a six-line list is cheaper than correcting a built page.
4. Connect PageFly and hand over the list. With the connector on (the five steps above), paste the section list and ask for the page unpublished. Claude reads the authoring guide, searches the template library for a section that already matches, pulls your real product photos from your store's media, and adds the sections in order. Every element it writes is a PageFly element — a PageFly heading, a PageFly image, a PageFly button — because the authoring guide is the only vocabulary it is allowed to write in. That is why the result opens in the PageFly editor as an ordinary page and not as a block of imported code.
5. Open the preview and fix in place. A preview link comes back after each section, rendered inside your live theme rather than an approximation of it. Where it is wrong, say so section by section — "the offer band needs the price bigger and the subtitle shorter" — and the change lands on that section only.
6. Publish when you are ready. Nothing reaches the storefront until you ask for it. If the page needs a cleaner URL first, rename the handle before publishing, not after, so you are not fixing links later.

Two honest limits. A page tops out at 10 sections, so a very long campaign page is two pages or a hand-finished one. And the design step is a thinking aid, not a converter: Claude is reading your design to write a brief, not exporting it. The page it builds is composed from PageFly sections, which is exactly why you can still edit it by hand afterwards.

What the connector can and cannot touch

An assistant that can change your live pages deserves a hard look at its permissions. Five facts, and they are the ones that matter:

• One store, approved by you. Access is scoped to the single Shopify store you approve inside your own Shopify admin.
• Nothing goes live by accident. Pages the assistant creates are unpublished, and stay unpublished until publish_page is explicitly called.
• Deleting is not destroying. A page the assistant deletes goes to PageFly's trash, exactly as it would if you deleted it in the PageFly dashboard.
• No customer data. The connector reads no customer, order or payment data. Checkout, discounts, inventory, admin settings, other apps' data and other stores are all out of reach.
• Revocable in two clicks. In PageFly, go to Preferences → Account → AI assistant connector and choose Disconnect all to revoke every token immediately. Do that before uninstalling PageFly, not after.

Read the full breakdown in the connector's data, permissions and security doc.

Claude, ChatGPT, Sidekick and FlyMate

The same connector works in ChatGPT on a paid plan with Developer mode enabled, and in any other MCP-compatible client — one endpoint, several assistants. The setup for each is in Use the PageFly MCP server in ChatGPT and other assistants.

Where it differs from what you may already have: PageFly in Shopify Sidekick can now build a new PageFly page from a chat and report on your pages, health scores and test results, but it cannot edit, publish or delete pages. FlyMate is PageFly's own assistant inside the editor, working on the page in front of you — and since the connector now uses the same editing engine FlyMate does, the difference is where you are sitting, not what the assistant is allowed to do. The Claude connector is the one that takes a brief in a chat window and comes back with a built page. If you are still deciding which assistant should run which job, we compared them in Sidekick vs ChatGPT vs Claude.

"Sidekick is there to proactively identify new ways to grow." Vanessa Lee, VP of Product at Shopify, announcing the Winter '26 Edition (shopify.com)

That is the direction the whole category is moving: assistants that find the work, not just describe it. The gap the PageFly connector closes is the last one — letting the assistant do the page, on a store where you still hold the publish button. It is the same argument we make about Shopify AI agents generally.