English Français العربية

co.flow2/flow2

Official registry Media and design

Design mobile-first presentations — create, edit, preview, and publish from your AI.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http flow2 'https://mcp.flow2.co/'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "flow2": {
            "type": "http",
            "url": "https://mcp.flow2.co/"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Flow2 MCP Server
  2. Quick start
  3. What it can do
  4. Example prompts
  5. Authentication
  6. Privacy & data handling
  7. Support
  8. License

Flow2 MCP Server

Design mobile-first presentations - create, edit, preview, and publish from your AI assistant.

This is the official Model Context Protocol server for Flow2. It lets AI assistants like Claude work with your Flow2 account directly: spin up new flows, add and edit screens, drop in blocks, preview the result, and publish — all from a chat prompt.

  • Endpoint: https://mcp.flow2.co/
  • Transport: streamable-http
  • Auth: OAuth 2.1 with Dynamic Client Registration (RFC 7591)
  • Registry: co.flow2/flow2

Quick start

Claude Code (and Cowork)
claude mcp add --transport http flow2 https://mcp.flow2.co/ --scope user

Then run /mcp inside Claude Code to complete the OAuth sign-in.

Claude.ai (web + desktop)

Settings → Connectors → Add custom connector → URL: https://mcp.flow2.co/. Click Connect to authorize.

Cursor

In ~/.cursor/mcp.json:

{
  "mcpServers": {
    "flow2": {
      "url": "https://mcp.flow2.co/"
    }
  }
}
Other MCP-compatible clients

Any client that supports remote streamable-HTTP MCP servers can connect using the URL above. OAuth is handled automatically when the client supports DCR.

What it can do

The Flow2 MCP server exposes the full flow-authoring surface as tools:

ToolWhat it does
create_flowCreate a new Flow2 presentation
update_flow_metaRename or update flow-level metadata
get_flowRead the current state of a flow
add_screenAdd a new screen to a flow
get_screenRead a screen and its blocks
delete_screenRemove a screen from a flow
add_blockAdd a block (text, image, button, etc.) to a screen
patch_blockUpdate an existing block's content or styling
delete_blockRemove a block from a screen
get_blocks_schemaList available block types and their schemas
get_previewGet the screenshot URL for a single screen
render-flow-previewShow the whole flow inline in chat — vertical-scroll preview of all screens with theme-accent indicator (interactive on Apps-aware clients)
render-screen-previewShow a single screen inline in chat as a phone-framed screenshot
list_jobs / check_job_statusTrack long-running operations
check_creditsCheck the remaining credits on your account

All write tools are annotated with destructiveHint: false where appropriate so AI clients can reason about safety. Read-only tools are marked readOnlyHint: true.

Inline previews (Apps-aware clients)

On clients that support the MCP Apps extension (Claude.ai web + desktop, Claude Code, ChatGPT, Cursor, VS Code), render-flow-preview and render-screen-preview produce an interactive inline preview rendered inside a sandboxed iframe — no need to leave the chat to see your flow. CTA buttons on individual screens become click-through links; the indicator picks up the flow's theme accent color. Other clients fall back to the cover screenshot.

Example prompts

Once the server is connected, try:

  • "Create a new mobile pitch deck for my fintech app called 'Lumen'."
  • "Add a hero screen with a bold headline and a 'Get started' button."
  • "Generate three product-feature screens with icons and short captions."
  • "Show me my latest flow." (renders the inline preview)
  • "Preview screen 3 of my pricing flow."
  • "Share the link to my latest flow."

The assistant will call the right MCP tools, and you'll see the changes reflected in your Flow2 account in real time.

Authentication

The server implements OAuth 2.1 with Dynamic Client Registration. When you connect from a new client, it:

  1. Discovers /.well-known/oauth-authorization-server
  2. Registers itself as a client via the registration_endpoint
  3. Walks you through the standard authorization-code flow with PKCE
  4. Stores a refresh token for ongoing access

You can revoke a client at any time from your Flow2 account settings.

Privacy & data handling

  • Scope: the MCP server only accesses Flow2 data belonging to the authenticated user.
  • Logging: request metadata (tool name, timestamp, status) is logged for operational purposes; tool argument and response bodies are not retained beyond the request lifecycle.
  • Third-party services: Flow2 uses a small set of infrastructure providers (hosting, error tracking) — see the Privacy Policy for the full list.
  • Retention: authentication tokens are stored encrypted at rest; revoking access from your Flow2 settings purges them.

Full details: Privacy Policy · Terms of Service.

Support

License

MIT — see LICENSE.

Frequently asked questions

What is co.flow2/flow2?

Design mobile-first presentations — create, edit, preview, and publish from your AI.

How do I install co.flow2/flow2?

It runs as a remote server. In Claude Code: claude mcp add --transport http flow2 'https://mcp.flow2.co/'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does co.flow2/flow2 need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is co.flow2/flow2 open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains co.flow2/flow2?

It is published by flowboard. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.