Design mobile-first presentations — create, edit, preview, and publish from your AI.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"co-flow2-flow2": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Design mobile-first presentations — create, edit, preview, and publish from your AI assistant.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Apify MCP Server
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
MCP proxy that compresses prose fields (tool descriptions, etc.) using caveman rules. Same accuracy, fewer context tokens.
MCP Security Weekly
Get CVE alerts and security updates for co.flow2/flow2 and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
https://mcp.flow2.co/streamable-httpco.flow2/flow2claude mcp add --transport http flow2 https://mcp.flow2.co/ --scope user
Then run /mcp inside Claude Code to complete the OAuth sign-in.
Settings → Connectors → Add custom connector → URL: https://mcp.flow2.co/. Click Connect to authorize.
In ~/.cursor/mcp.json:
{
"mcpServers": {
"flow2": {
"url": "https://mcp.flow2.co/"
}
}
}
Any client that supports remote streamable-HTTP MCP servers can connect using the URL above. OAuth is handled automatically when the client supports DCR.
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.
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.
Once the server is connected, try:
The assistant will call the right MCP tools, and you'll see the changes reflected in your Flow2 account in real time.
The server implements OAuth 2.1 with Dynamic Client Registration. When you connect from a new client, it:
/.well-known/oauth-authorization-server