{
  "markdown": "# Flow2 MCP Server\n\n> Design mobile-first presentations - create, edit, preview, and publish from your AI assistant.\n\nThis is the official [Model Context Protocol](https://modelcontextprotocol.io) server for [Flow2](https://flow2.co). 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.\n\n- **Endpoint:** `https://mcp.flow2.co/`\n- **Transport:** `streamable-http`\n- **Auth:** OAuth 2.1 with Dynamic Client Registration (RFC 7591)\n- **Registry:** [`co.flow2/flow2`](https://registry.modelcontextprotocol.io/servers/co.flow2/flow2)\n\n---\n\n## Quick start\n\n### Claude Code (and Cowork)\n\n```bash\nclaude mcp add --transport http flow2 https://mcp.flow2.co/ --scope user\n```\n\nThen run `/mcp` inside Claude Code to complete the OAuth sign-in.\n\n### Claude.ai (web + desktop)\n\nSettings → **Connectors** → **Add custom connector** → URL: `https://mcp.flow2.co/`. Click **Connect** to authorize.\n\n### Cursor\n\nIn `~/.cursor/mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"flow2\": {\n      \"url\": \"https://mcp.flow2.co/\"\n    }\n  }\n}\n```\n\n### Other MCP-compatible clients\n\nAny client that supports remote streamable-HTTP MCP servers can connect using the URL above. OAuth is handled automatically when the client supports DCR.\n\n---\n\n## What it can do\n\nThe Flow2 MCP server exposes the full flow-authoring surface as tools:\n\n| Tool | What it does |\n|---|---|\n| `create_flow` | Create a new Flow2 presentation |\n| `update_flow_meta` | Rename or update flow-level metadata |\n| `get_flow` | Read the current state of a flow |\n| `add_screen` | Add a new screen to a flow |\n| `get_screen` | Read a screen and its blocks |\n| `delete_screen` | Remove a screen from a flow |\n| `add_block` | Add a block (text, image, button, etc.) to a screen |\n| `patch_block` | Update an existing block's content or styling |\n| `delete_block` | Remove a block from a screen |\n| `get_blocks_schema` | List available block types and their schemas |\n| `get_preview` | Get the screenshot URL for a single screen |\n| `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) |\n| `render-screen-preview` | Show a single screen inline in chat as a phone-framed screenshot |\n| `list_jobs` / `check_job_status` | Track long-running operations |\n| `check_credits` | Check the remaining credits on your account |\n\nAll write tools are annotated with `destructiveHint: false` where appropriate so AI clients can reason about safety. Read-only tools are marked `readOnlyHint: true`.\n\n### Inline previews (Apps-aware clients)\n\nOn clients that support the [MCP Apps extension](https://modelcontextprotocol.io/extensions/apps) (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.\n\n---\n\n## Example prompts\n\nOnce the server is connected, try:\n\n- *\"Create a new mobile pitch deck for my fintech app called 'Lumen'.\"*\n- *\"Add a hero screen with a bold headline and a 'Get started' button.\"*\n- *\"Generate three product-feature screens with icons and short captions.\"*\n- *\"Show me my latest flow.\"* (renders the inline preview)\n- *\"Preview screen 3 of my pricing flow.\"*\n- *\"Share the link to my latest flow.\"*\n\nThe assistant will call the right MCP tools, and you'll see the changes reflected in your Flow2 account in real time.\n\n---\n\n## Authentication\n\nThe server implements OAuth 2.1 with Dynamic Client Registration. When you connect from a new client, it:\n\n1. Discovers `/.well-known/oauth-authorization-server`\n2. Registers itself as a client via the `registration_endpoint`\n3. Walks you through the standard authorization-code flow with PKCE\n4. Stores a refresh token for ongoing access\n\nYou can revoke a client at any time from your Flow2 account settings.\n\n---\n\n## Privacy & data handling\n\n- **Scope:** the MCP server only accesses Flow2 data belonging to the authenticated user.\n- **Logging:** request metadata (tool name, timestamp, status) is logged for operational purposes; tool argument and response bodies are not retained beyond the request lifecycle.\n- **Third-party services:** Flow2 uses a small set of infrastructure providers (hosting, error tracking) — see the [Privacy Policy](https://flow2.co/static/privacy) for the full list.\n- **Retention:** authentication tokens are stored encrypted at rest; revoking access from your Flow2 settings purges them.\n\nFull details: [Privacy Policy](https://flow2.co/static/privacy) · [Terms of Service](https://flow2.co/static/tos).\n\n---\n\n## Support\n\n- **Email:** [email protected]\n- **Issues:** [github.com/flowboard/flow2-mcp/issues](https://github.com/flowboard/flow2-mcp/issues)\n\n---\n\n## License\n\nMIT — see [LICENSE](./LICENSE).\n",
  "bytes": 5113,
  "sha": "42806c6da3f92cbca3d02cfc236727e0d7daee7b104a03691ef8db3d051217cf",
  "repo_slug": "flowboard/flow2-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_co_flow2_flow2_9dbe8bc4/readme"
}