The AwesomeFlows MCP
A hosted server over the whole library. Plain language in; real storefront screens and every interaction state out.
Loading
The AwesomeFlows MCP
Real ecom patterns, piped into your AI tools
A hosted server over the whole library. Plain language in; real storefront screens and every interaction state out.
any MCP client
$ claude mcp add --transport http awesomeflows https://awesomeflows.com/api/mcp
awesomeflows connected
> find cart drawers with a free-shipping progress bar
searching 1415 live storefronts
6069 cart captures returned · looping clips inline
Endpoint: awesomeflows.com/api/mcp · Pro accounts only · sign in from your own tool to connect
Three steps to connect
No keys to paste, no config to hand-edit. One command, an OAuth sign-in, and the library answers your tool directly.
- 01
Add the server
The MCP is a hosted Streamable HTTP server, no package to install. In Claude Code, one command registers it. In Claude on the web or desktop, add it under Settings → Connectors → Add custom connector with the same URL. Any other MCP client: point it at the endpoint over HTTP.
claude mcp add --transport http awesomeflows https://awesomeflows.com/api/mcp - 02
Ask in plain language
Three tools come back from the handshake: search_ecom_patterns finds screens by describing them ("sticky add to cart", "free shipping progress bar"), get_flow returns a store's whole journey as ordered, annotated steps, and list_library tells your assistant what stores and flows actually exist before it searches. Just ask, your assistant picks the tool.
- 03
Pro accounts only
The MCP is a Pro feature. Connect it once and your agent searches the whole library — every store, every flow, the full capture history. Free accounts browse the same captures on the web instead.
Connect it to Claude
The 60-second Claude walkthrough
Claude Code (CLI)
One command in your terminal, then ask away in any session:
claude mcp add --transport http awesomeflows https://awesomeflows.com/api/mcpClaude on web + desktop
Settings → Connectors → Add custom connector. Name it AwesomeFlows and paste the endpoint URL:
https://awesomeflows.com/api/mcpAny other MCP client
Add a server with the Streamable HTTP transport pointing at the same URL. Cursor, Windsurf, and friends all take a url-type entry.
{ "url": "https://awesomeflows.com/api/mcp" }Then just ask: "show me sticky add-to-cart bars from the AwesomeFlows library" and Claude calls search_ecom_patterns and renders the returned screens inline.
What comes back
Not links. The actual screens
page before add to cart
allbirds.com · 2026-10-26Add to Cart
reebok.com · 2026-10-26Checkout: Contact Info
variants unselected
Agent-discoverable by design
Built to be the tool your agent reaches for
When an assistant needs to know what real e-commerce looks like, the answer should be one tool call away. We are shaping the server so agents surface it on their own.
A crisp, obvious name
One clear purpose, ecom design patterns, described so a model knows exactly when to reach for it.
Documented tools
Each tool ships with a plain description and typed arguments, so an agent can plan a call without guessing.
Sign in, no API keys
Connecting runs a standard OAuth flow in your browser. Approve it once and your agent is bound to your account — there's no key to paste, leak, or rotate.
The MCP is the headline Pro feature
Free browses the library on the web. Pro pipes it into your tools through the MCP. Pro is $12/mo, cancel whenever.
New in the library, daily
Get the newest sites first
A short daily email whenever a new storefront joins the library, no spam, unsubscribe anytime.