Platform Access lets you build FlowFn programmatically — create, update and list your apps, agents, streams, data sheets, playgrounds, forms, workflows and visualizers, and list a team's platform connections. It's the same set of authoring actions over two surfaces that share one credential:
- REST API —
/v1. Call it from Postman, curl or your own app. Import the OpenAPI spec at/v1/spec.json. - Management MCP server —
/mcp/manage/v1. Add it to Claude.ai, ChatGPT or Cursor as a remote connector and ask the AI to build for you.
This is the control-plane authoring API. It is different from the per-app MCP host (/mcp/v1/:code), which exposes an app's runtime tools rather than authoring your artifacts.
Get a token
Open My Account → Security → Platform Access and click Generate token. The token looks like flowfn_pat_… and is shown once — copy it immediately. It's stored hashed, so if you lose it you rotate to get a new one. The same token authenticates both the REST API and the MCP server; rotating or revoking it cuts off both surfaces on the next request.
Every call runs as you, honouring your team role and plan limits — the API can only do what you can do in the dashboard. Authoring calls are free (no credits), bounded by your plan's per-artifact limits and a per-token rate limit. The REST API and the management MCP are each an opt-in plan feature, so your plan may include one, both, or neither.
Choosing a team
Every action targets a team. If you belong to one team it's used automatically; otherwise name it — the X-Team-Id: <team-id> header (REST) or the team_id argument (MCP). Not sure of your team id? Call GET /v1/teams (REST) or the list_teams tool (MCP). Most artifacts live under an app — omit app_id to use the team's first app (one is created automatically if the team has none), or pass a specific app_id.
Continue
- REST API reference — base URL, endpoints, curl examples, error envelope.
- Management MCP — connect Claude.ai / ChatGPT / Cursor, the tool catalog.