Flow2

co.flow2Published by flow2.coOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow Media & Design

Server details

Identifier: co.flow2/flow2
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to flow2.co, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/co.flow2%2Fflow2.svg)](https://sourceweft.com/mcp/co.flow2%2Fflow2?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Flow2's remote MCP server lets an AI assistant create, edit, preview and publish mobile-first presentations in your Flow2 account from chat.

What you can do: Create and manage flows: create a presentation, rename or update its metadata, read its current state, and track long-running jobs or remaining credits. Manage screens: add, read and delete screens within a flow. Manage blocks: add text, image, button and other blocks to a screen, update their content or styling, delete them, and list available block types and schemas. Preview and publish: get a screenshot URL for a screen, render a whole flow or a single screen inline in chat, and publish the result.
When to use it: Useful when you want to draft or revise a mobile-first presentation, pitch deck or product flow conversationally and see previews without leaving the chat, rather than building it by hand in Flow2.
Requirements: A remote streamable-HTTP endpoint; no local package or runtime. A Flow2 account with OAuth 2.1 sign-in (Dynamic Client Registration supported); clients without DCR need manual authorization. An MCP client that supports remote HTTP servers.

Before you install

The server can write to your Flow2 account: it creates, edits and deletes flows, screens and blocks, and can publish presentations. It checks and consumes account credits. OAuth grants ongoing access via a refresh token; revoke clients in Flow2 account settings if no longer needed. Request metadata is logged, and Flow2 uses third-party hosting and error-tracking providers.

Installation

In SourceWeft

Open Flow2 in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.flow2%2Fflow2/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "flow2": {
      "type": "http",
      "url": "https://mcp.flow2.co/"
    }
  }
}

README

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)

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:

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:

Tool	What it does
`create_flow`	Create a new Flow2 presentation
`update_flow_meta`	Rename or update flow-level metadata
`get_flow`	Read the current state of a flow
`add_screen`	Add a new screen to a flow
`get_screen`	Read a screen and its blocks
`delete_screen`	Remove a screen from a flow
`add_block`	Add a block (text, image, button, etc.) to a screen
`patch_block`	Update an existing block's content or styling
`delete_block`	Remove a block from a screen
`get_blocks_schema`	List available block types and their schemas
`get_preview`	Get the screenshot URL for a single screen
`render-flow-preview`	Show the whole flow inline in chat — vertical-scroll preview of all screens with theme-accent indicator (interactive on Apps-aware clients)
`render-screen-preview`	Show a single screen inline in chat as a phone-framed screenshot
`list_jobs` / `check_job_status`	Track long-running operations
`check_credits`	Check 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:

Discovers /.well-known/oauth-authorization-server
Registers itself as a client via the registration_endpoint
Walks you through the standard authorization-code flow with PKCE
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

Email: [email protected]
Issues: github.com/flowboard/flow2-mcp/issues

License

MIT — see LICENSE.

Source: README.md at commit d77464d

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.