Flows Docs | Connect Your AI with Flows MCP

01What is Flows MCP

Flows exposes your site to AI models over the Model Context Protocol — an open standard that lets an AI tool call real, permissioned functions. Once connected, your model can read your brand context, see what your site looks like, and ship custom article components — hero banners, tables of contents, TL;DRs, takeaways, FAQs, sources and related-article blocks, plus the whole listing page — straight into your Flows studio.

You describe what you want in plain language, in the tool you already work in. Flows handles rendering, sanitising, and serving the result on your real articles — crawlable and fast.

02Requirements

A Flows account with at least one connected site (connect one in the dashboard first).
An MCP-capable client — Claude, Claude Code, Cursor, ChatGPT, Windsurf, VS Code, or anything that supports remote MCP servers over Streamable HTTP.
That's it. Auth is OAuth — your client walks you through it on first use. No API keys to create or paste.

03Connect in a minute

Everything runs through one server URL:

https://www.flowcrews.com/mcp

Add the URL to your AI tool's MCP / connector settings (see below for where that lives in your client).
Your tool opens a secure Flows sign-in — approve it once.
Ask for a component. It appears in your Flows studio, live.

Tip: ask whoami first — if it returns your account email, the connection is working.

04Any MCP client

Every MCP client connects the same way — there's nothing tool-specific to learn. Claude, ChatGPT, Grok, Cursor, Windsurf, VS Code, and anything else that supports remote MCP servers over Streamable HTTP all point at the one URL:

https://www.flowcrews.com/mcp

Clients with a connectors / MCP settings panel take the URL directly — add a custom connector or server and paste it in. Clients that use a JSON config file add a server entry with the same URL:

{
  "mcpServers": {
    "flows": {
      "url": "https://www.flowcrews.com/mcp"
    }
  }
}

Either way, OAuth is handled for you: your client opens a Flows sign-in the first time it calls a tool — approve it once and you're connected. No API keys, nothing to configure per client.

05From the Wix or Shopify app

Installed Flows from the Wix App Market or the Shopify App Store, and working inside that app? Then you have no separate Flows sign-in — your identity is your Wix or Shopify session. So you skip OAuth entirely and connect with a personal link for your site instead of the universal URL above.

In the app, open Crew Studio and choose Setup MCP. It shows a link that's unique to your site, shaped like this:

https://www.flowcrews.com/mcp?pair=…

Paste it into your client exactly like the universal URL — but there's no sign-in step, and it only ever touches that one site. It carries its own token, so keep it in your client's config like an API key; disconnecting or uninstalling the app revokes it instantly. Always copy the real link from the Setup MCP page — the one above is just the shape.

06Your first component

Once connected, just describe what you want. A good first prompt:

Use Flows to build me a glassmorphic "Key Takeaways" component
with staggered reveal animations, matched to my brand accent.

A capable model will typically:

Call get_authoring_guide to learn your brand colours, logo and the component token/behaviour palette.
Optionally call get_site_screenshot to see your site's current look.
Design and save the component with create_or_update_component — or several takes at once with create_component_variants.

The design lands in your Flows studio, where you can preview it live, switch variants, and control what actually renders on your articles.

07Tool reference

Eleven tools, split between reading your site and writing designs to it.

whoamiread

Confirms who's connected — returns your account id and email. The quickest "is this working?" check.

list_my_sitesread

Lists the Flows sites you own — id, name, domain, platform and niche.

list_component_typesread

The buildable slots — hero banner, table of contents, TL;DR, takeaways, FAQ, sources and related articles — plus the full listing page, each with the data tokens it can bind.

list_behaviorsread

The built-in interactivity library (accordion, tabs, carousel, reveal, scrollspy, lightbox) and the markup that activates each.

get_authoring_guideread

The full authoring palette plus your site's brand context — name, colours, logo — so designs come out on-brand.

get_site_screenshotread

A screenshot of your site's homepage (above the fold, or fullPage for more) so the model can see what it's designing against.

create_or_update_componentwrite

Saves a custom design — HTML with tokens, dark/light CSS, optional scripted interactions — to one of your site's slots. Pass the design's id back to refine it.

create_component_variantswrite

Saves two to six takes on a design in one call — the first becomes the default, the rest are alternates you can compare and switch between.

set_active_componentwrite

Promotes a saved design to the live one for its slot — how you swap between variants.

delete_componentwrite

Removes a saved design by id.

configure_listing_pagewrite

Updates your article-library page's title, subtitle, SEO title/description and social-share image.

08Working across sites

Every tool takes an optional instanceId. You almost never need it:

One site — tools resolve to it automatically. Just ask.
Several sites — the tool replies with your site list and the model asks which one you mean. Name the site in your prompt ("…on my cooking blog") and it carries on.

Writes only ever succeed on sites your account owns.

09Authentication

Flows MCP uses OAuth 2.1 with PKCE and dynamic client registration — the modern MCP auth standard. When your client first connects, it opens a Flows sign-in; you approve access to your email and profile, and the client manages tokens from there. There are no API keys to create, store, or leak.

Every tool call is verified server-side against your Flows account. Signing out of the connector in your client ends its access.

Merchants working inside the Wix or Shopify app connect with a per-site link instead of OAuth — see From the Wix or Shopify app. It's scoped to that one site and revoked instantly when you regenerate it or uninstall.

10Permissions & scope

Ownership-scoped: the connection can only read and write sites owned by your account — every write re-checks ownership on the server.
Narrow writes: tools save component designs and listing-page metadata. They can't touch billing, subscribers, orders, or account settings.
Sanitised output: saved designs go through the same sanitising pipeline as everything else in the studio before they render on your articles.
Plan-aware: creating a new custom component counts against your plan's custom-component allowance. If you're over it — or your plan doesn't include custom components — the write is declined with an upgrade note, and nothing partial is saved.

11Troubleshooting

"Unauthorized" from every tool — the OAuth handshake didn't finish. Remove and re-add the connector, and complete the Flows sign-in when it opens.
"No sites" — your Flows account has no connected site yet. Connect one in the dashboard, then try again.
"Choose a site" — you own several sites; tell the model which one you mean.
"Limit reached" — you're at your plan's custom-component allowance, or your plan doesn't include custom components. Delete an old design, or upgrade your plan.
Client can't find the server — double-check the URL is exactly https://www.flowcrews.com/mcp and that your client supports remote MCP servers (Streamable HTTP), not just local ones.

Still stuck? Ask Sam — the chat bubble on this page — or reach us from the dashboard.