Apps MCP tools

The Apps library is a reference collection of real iOS and web apps: screens from each app's latest version, tagged by pattern ("Onboarding", "Paywall", "Checkout") and UI element ("Tab Bar", "Card"), recorded user flows with where the user tapped, and App Store screenshots. Agents see every screen as an image, with the text on it.

Floo Apps is a separate MCP server with only these tools. Add it when your agent designs somewhere else, such as in your codebase or another design tool, and you want real screens as reference without the canvas tools. Agents connected to the full Floo server already have the same tools.

Connect

Claude Code:

claude mcp add --transport http --scope user floo-apps https://worker.floo.design/mcp/apps

Codex:

codex mcp add floo-apps --url https://worker.floo.design/mcp/apps
codex mcp login floo-apps

Cursor, Windsurf, Cline and other JSON clients:

{
  "mcpServers": {
    "floo-apps": {
      "type": "http",
      "url": "https://worker.floo.design/mcp/apps"
    }
  }
}

Claude and ChatGPT: add a custom connector or MCP server named Floo Apps with the address above, exactly as on the Claude and ChatGPT pages. The library is open to every signed-in Floo account; the agent reads it as you.

What to ask

• "Look at three good paywalls, then build ours in our React components."
• "How does Calm onboard new users? Walk me through the flow."
• "Find iOS settings screens with a grouped list and copy their structure, not their style."
• "Put Careem's subscription flow on my Floo canvas as references."

The agent finds the app or screen type, studies what it sees, and designs its own version. The screens belong to their owners: agents use them as references only and never embed, trace or ship them.

Tools

Every read tool shows screens as images by default (at most 12 per call: list previews at 512 px, a single screen at 1024 px). Pass images: false to get the data only, which is faster and uses less context.

search_catalog_apps

Find apps and websites by name, tagline or category ("calm", "budgeting", "food delivery"), most reviewed first. Read-only.

Returns each app's slug (use it in the other tools), name, tagline, platform, categories, screen and flow counts, and its page in the library.

get_catalog_app

Open one app's latest version. Read-only.

Returns the version and its release date, the app's patterns and UI elements with how many screens show each ("Onboarding (12)"), its key screens (shown as images), its recorded flows (open one with get_catalog_flow), and its App Store screenshots with ids like preview:123, which add_catalog_screens also accepts.

search_catalog_screens

Find screens across apps, or inside one app, and see them. The query matches the screen's title, its patterns, its UI elements and the text on it. Across apps, key screens come first; inside one app, screens come in the app's order. Read-only.

Returns each screen's id, app, title, patterns, UI elements, size in points, image URL and library page, plus next_offset when there may be more.

get_catalog_screen

Look at one screen up close. Read-only.

Returns everything search_catalog_screens does, plus the flows the screen is part of and the text on it (from OCR, up to 1,500 characters; it can be noisy, but it is real copy and shows content density).

get_catalog_flow

Walk through a recorded user flow, such as onboarding, sign-up or checkout. Read-only.

Returns the flow's name and app, the actions in it, its screen recording, and every step in order with its screen and the tap area (x, y, width and height as fractions of the screen, 0 to 1).

add_catalog_screens

Place screens or App Store screenshots on a Floo canvas page as image frames at device size, side by side to the right of what is already there. They are references to design next to, never the design itself.

Needs edit access to the canvas. Returns how many frames were added (and skipped, for ids not in the library) and a summary of each new frame.

get_profile

The account the connection acts as: its id and display name. Read-only.

Limits and permissions

• The tools read the library as the signed-in person; any Floo account can use it.
• Only add_catalog_screens changes anything, and only on canvases the person can edit.
• The full list of canvas tools is in MCP tools. Use of the library is covered by the Terms of Service.