Flow2 MCP Server

A Model Context Protocol server that lets Claude (or any MCP-compatible assistant) create, read, and edit Flow2 presentations directly from chat.

The fastest way to draft a mobile presentation is to talk through the content first, then take it the last mile in an editor. The Flow2 MCP server turns Claude into the drafting surface. "Make a 7-slide pitch for a B2B SaaS product targeting eng leaders" returns a real, themed, mobile-first flow in under a minute. "Rewrite slide 3 to lead with the metric, not the explanation" edits it in place. When you're ready to polish images, swap themes, or add the final CTA, the same flow opens in the editor at flow2.co/m/<id>/edit.

Submitted to Anthropic's Connectors Directory. Listing pending review — in the meantime, add it manually in any Claude surface using the URL below.

What it looks like in Claude

A Flow2 presentation rendered inline inside a Claude conversation

Each generated flow returns a live mobile preview directly inside the chat — scroll the screens, see the theme, click through. The render works in Claude.ai web, Claude Desktop, and the Cowork iframe.

Connect it
Endpoint https://mcp.flow2.co/
Auth OAuth 2.1 with PKCE — no API key paste required
Tools 14 (8 read-only, 6 writes)

Claude.ai (web) and Claude Desktop

  1. Open claude.ai/settings/connectors
  2. Click Add custom connector
  3. Paste https://mcp.flow2.co/
  4. Sign in with your Flow2 account when prompted

Claude Desktop reads from the same connector list — set it up once, it shows up in both.

Claude Code (CLI)

claude mcp add flow2 https://mcp.flow2.co/

First tool call opens the OAuth flow in your browser.

ChatGPT

ChatGPT supports MCP connectors too. Use the same endpoint — https://mcp.flow2.co/ — and the same OAuth sign-in.

Local stdio (for clients without remote MCP support)

For environments that can't talk remote MCP yet, the server can also run locally over stdio with an API token. Setup is on GitHub: flowboard/flow2-mcp.

What you can do

Action Example prompt
Generate "Make a 5-slide pitch for a B2B SaaS product targeting eng leaders."
Iterate "Rewrite slide 3 to lead with the metric, not the explanation."
Theme "Swap to the editorial theme — this needs to feel more serious."
Add a screen "Add a closing CTA asking them to book a 15-min demo."
Inspect "Show me the preview of slide 4."
Reformat (paste a long doc) "Turn this into a 10-slide deck."

The 14 tools split into 8 read-only (get_flow, get_screen, get_preview, check_credits, list_jobs, check_job_status, get_blocks_schema, two preview renders) and 6 writes (create_flow, update_flow_meta, patch_block, add_block, add_screen, plus the two destructive delete_*). Destructive tools are flagged as such so Claude asks before running them.

Iterate in Claude, polish in the editor

The two surfaces are complementary, not redundant.

Claude is good at the structure — content order, voice, deciding whether the third slide is actually the strongest opener. The editor is good at the last 20% — the one chart that should be a stat instead, the exact image, theme nudges, the link that goes on the CTA. Every flow generated through MCP opens in the editor at the URL Claude returns — same flow, no export step.

How auth works

OAuth 2.1 with PKCE. The first tool call kicks off a browser-based sign-in to your Flow2 account; the resulting token lives in the MCP client, not in our docs. We never see your password. The token is scoped to presentations and credits and can be revoked from Flow2 account settings.

For the curious: full OAuth metadata is at flow2.co/.well-known/oauth-authorization-server. Dynamic Client Registration (RFC 7591) is supported, so any compliant MCP client can register itself without a manual app secret.

Credits

MCP tool calls draw from the same credit pool as the web UI.

Action Cost
create_flow (full generation) 10 credits
Image generation 2 credits per image
Block edits, reads, theme changes Free

Free accounts: 50 credits at signup. Pro: 500 credits/month. Check balance with check_credits or at flow2.co/account/billing.

Privacy

The MCP server logs request metadata (tool name, timestamp, status, OAuth client ID) for up to 30 days for reliability and abuse monitoring. Tool inputs are not persisted. Generated content lives in your Flow2 account and is deleted when you delete the flow. Full details in the Privacy policy under "AI Connectors and the flow2 MCP Server".

Links