---
name: awesomeflows-mcp
description: Find real e-commerce UX examples (homepages, product pages, carts, checkouts, search, filters) captured from live storefronts, via the AwesomeFlows MCP server. Use when designing or critiquing an online store and you want evidence of how real brands build a pattern.
---

# AwesomeFlows MCP

AwesomeFlows is a library of screens captured from live e-commerce storefronts
on a schedule, with every interaction state (drawers open, variants selected,
errors shown). The MCP server lets you search it in plain language and get the
screens back.

## Connect

- Endpoint: `https://awesomeflows.com/api/mcp` (MCP Streamable HTTP, JSON-RPC over POST)
- Auth: OAuth 2.1. An unauthenticated request gets a 401 whose
  `WWW-Authenticate` header points at the protected resource metadata
  (`https://awesomeflows.com/.well-known/oauth-protected-resource/api/mcp`); your MCP client runs the sign-in from there.
- Plan: tool calls need an AwesomeFlows Pro account ($12/mo). A
  signed-in free account gets a message explaining how to upgrade. Relay it to
  the user; retrying will not change the answer.
- Setup guide for people: https://awesomeflows.com/mcp

Claude Code: `claude mcp add --transport http awesomeflows https://awesomeflows.com/api/mcp`

## Tools

- `search_ecom_patterns`: natural-language search across the library.
  Start here. Filter by store, flow or category when the user names one.
  Queries for a specific UI element ("free shipping progress bar", "size
  chart", "cart drawer") match best.
- `get_flow`: every step and state of one captured flow, when a
  search result looks right and you need the full sequence.
- `list_library`: which stores, flows and named patterns exist.
  Use it when a search comes back empty, to find the library's own words.
- `list_collections` / `get_collection`: the
  user's own saved collections, when they refer to screens they saved.

All tools are read-only.

## What the library covers

Patterns: Homepage, Navigation / Mega Menu, Product Listing (PLP), Collections Index, Sale / Clearance, Product Detail (PDP), Size / Fit Guide, Cart, Checkout, Search, Filter / Facets, Newsletter / Email Capture. Results are desktop captures (1440px wide) by default.
Pass `device: "mobile"` to `search_ecom_patterns` or `get_flow` for phone
captures (390px wide) of the homepage, product listing, product page, cart and
checkout, available for almost every store (there are no mobile search
captures). Only present a result as mobile evidence when it came from a mobile
request.

## Good use

- Cite the store and flow for every example you show, so the user can open it.
- Compare two or three stores rather than describing one as "the" way.
- If a search is empty, the response suggests the nearest real term; retry
  with it instead of guessing.