MCP server

Flowy ships a hosted MCP server at:

https://mcp.tryflowy.ai/mcp

It speaks Streamable HTTP (the current MCP transport) and authenticates over OAuth. No API key to copy anywhere. Point a compatible agent at the URL, sign in and consent once in the browser, and the connection is bound to your Flowy account: by default every tool call acts in and bills your personal account wallet, and can act in any workspace you can manage by passing a workspace_id (from list_workspaces).

Discovery flow

An MCP client never needs the OAuth details hardcoded. It discovers them from the server itself, per the MCP authorization spec:

Unauthenticated request

The client POSTs to /mcp with no bearer token.

401 challenge

The server responds 401 with a WWW-Authenticate: Bearer resource_metadata="…" header pointing at its protected-resource metadata.

Protected-resource metadata (RFC 9728)

The client fetches that URL and reads authorization_servers (which authorization server to use) and scopes_supported.

Authorization-server metadata (RFC 8414)

The client fetches /.well-known/oauth-authorization-server on that authorization server (mirrored on the MCP server’s own origin) to learn the authorize, token, and registration endpoints.

Dynamic client registration (RFC 7591)

The client registers itself against the registration endpoint and gets back a client_id, with no manual app setup required.

Authorize with PKCE

The client opens the authorize URL with a PKCE challenge. You sign in (if needed) and see the consent screen: the same one described in OAuth apps, and approve.

Token exchange

The client exchanges the authorization code for an access token at the token endpoint.

Retry with the bearer

The client retries the original /mcp request with Authorization: Bearer <token>, and the session proceeds normally.

Every step above is automatic in an MCP-native client (Claude, Claude Code, Cursor, ChatGPT). You only ever interact with the sign-in + consent screen in step 6.

Scopes

The server requests this fixed set of scopes on every connection, matching the backend’s registration ceiling for MCP clients, so a client that requests exactly these gets the full tool surface below, flow creation included: apps:read · apps:write · runs:read · runs:write · generations:read · generations:write · assets:read · credits:read

This scope set is specific to the MCP server’s client registration. It isn’t the same list a third-party OAuth app can request from the console (that list adds elements:read / elements:write and omits apps:write).

Tools

The server exposes 38 tools, grouped by what they work with:

Community (3)

Tool	What it does
`list_community_templates`	Browse community templates, featured, or searched by query/category.
`get_community_template`	One template’s detail (description, remix/like/bookmark stats) plus similar templates.
`remix_community_template`	Clone a template into a new project in a workspace you choose.

Canvas (6)

Tool	What it does
`create_node`	Start a generation as a visible node on a project’s canvas.
`update_node`	Regenerate an existing node in place with a new prompt or settings.
`layout_canvas`	Auto-arrange a project’s nodes into a readable left-to-right layout.
`list_nodes`	List a project’s canvas nodes, read live from the collaboration document.
`get_node`	Poll one canvas node’s live status and output.
`connect_nodes`	Draw an edge so one node’s output feeds another as a reference.

Generation (5)

Tool	What it does
`generate_image`	Generate an image (spends credits).
`generate_video`	Generate a video (spends credits).
`generate_audio`	Generate audio: SFX or music (spends credits).
`generate_3d`	Generate a 3D model from 1–3 reference images (spends credits).
`get_generation`	Poll a generation’s status and read its output URLs.

Assets (2)

Tool	What it does
`list_assets`	Browse a workspace’s assets (images/videos/audio) with signed URLs.
`get_asset`	Fetch one asset by id with a fresh signed URL.

Account & billing (4)

Tool	What it does
`get_account`	The connected account: email, name, plan, account-wallet balance.
`get_credits`	A wallet’s credit balance (total, blocked, available).
`list_workspaces`	Every workspace the account can act in.
`list_transactions`	The account’s recent credit ledger.

Projects (2)

Tool	What it does
`list_projects`	List the workspace’s canvas projects.
`create_project`	Create a new canvas project.

Brand kits (6)

Tool	What it does
`list_brandkits`	List the workspace’s brand kits.
`get_brandkit`	Fetch one brand kit with full colors, fonts, logos, and design tokens.
`create_brandkit`	Extract a brand kit from a website URL (async).
`update_brandkit`	Partially update a brand kit’s fields.
`delete_brandkit`	Permanently delete a brand kit.
`poll_brandkit_extract`	Check the status of an extraction started by `create_brandkit`.

Renders (3)

Tool	What it does
`start_render`	Render a composition timeline (Remotion JSON) to a final video.
`get_render`	Get one render’s status by its workflow id.
`list_renders`	Recent composition renders with their video URLs.

Flows (5)

Tool	What it does
`list_flows`	List the published flows (reusable apps) in the workspace.
`get_flow`	One flow’s input/output schema.
`run_flow`	Start an async run of a flow (spends credits).
`get_run`	Poll a run’s status and, once complete, its outputs.
`create_flow`	Publish a canvas project as a reusable flow (requires `apps:write`).

Skills (2)

Tool	What it does
`list_skills`	List the Flowy skills: expert step-by-step workflows.
`load_skill`	Load one skill’s full instructions by name.

Connect from your agent

Claude Code
Cursor
Claude / Claude Desktop
ChatGPT
VS Code

claude mcp add --transport http --scope user flowy https://mcp.tryflowy.ai/mcp

Or run it for you with the CLI: flowy mcp install --client claude.

Add to ~/.cursor/mcp.json:

{ "mcpServers": { "flowy": { "url": "https://mcp.tryflowy.ai/mcp" } } }

Or run flowy mcp install --client cursor from the CLI.

In Settings → Connectors, add a custom connector with the URL https://mcp.tryflowy.ai/mcp. Claude discovers the OAuth flow automatically and prompts you to sign in.

Enable Developer mode, then Settings → Apps → Developer mode → add an MCP server with the URL https://mcp.tryflowy.ai/mcp.

Add an MCP server pointing at https://mcp.tryflowy.ai/mcp from the command palette’s MCP server configuration (Streamable HTTP transport). VS Code drives the OAuth discovery flow the same way.

Any other MCP-capable client can connect the same way: point it at https://mcp.tryflowy.ai/mcp over Streamable HTTP and let it run the discovery flow above.

Get started

Endpoints

Reference

Discovery flow

Scopes

Tools

Connect from your agent

​Discovery flow

​Scopes

​Tools

​Connect from your agent

Discovery flow

Scopes

Tools

Connect from your agent