The management MCP server is one of the two Platform Access surfaces — add it to an AI client as a remote connector and ask the AI to build FlowFn for you, calling the same authoring actions as the REST API (get a token here).
Endpoint & authentication
MCP endpoint: https://mcp.flowfn.com/mcp/manage/v1. Use your Personal Access Token as the bearer credential in your client's connector config (below). Every tool targets a team via its team_id argument — call list_teams first to find yours.
Connect an AI client
Claude Desktop / Cursor — add to your MCP config:
{
"mcpServers": {
"flowfn": {
"url": "https://mcp.flowfn.com/mcp/manage/v1",
"headers": { "Authorization": "Bearer flowfn_pat_YOUR_TOKEN" }
}
}
}
Claude Code CLI:
claude mcp add --transport http flowfn https://mcp.flowfn.com/mcp/manage/v1 \
--header "Authorization: Bearer flowfn_pat_YOUR_TOKEN"
Claude.ai / ChatGPT — add a custom connector using the endpoint URL above and your token as the bearer credential.
MCP tools
The server exposes the same actions as tools (about 26): list_teams, list_apps, create_app, list_connections, and list_/create_/update_ for agents, streams, playgrounds, forms, workflows and visualizers, plus the data-sheet tools list_databases, create_database, list_data_sheets, create_data_sheet, update_data_sheet, query_data_sheet_rows and insert_data_sheet_rows. On connect it tells the AI to call list_teams first and pass a team_id.
Good to know
- One token, both surfaces, one kill switch. Rotating or revoking your token (or an admin disabling it) stops both REST and MCP on the next request.
- Free authoring. Creating/updating via the API costs no credits — the same as building in the dashboard.
- Create / update / list only. There is no delete in this version; delete artifacts from the dashboard.
- Acts as you. Team role and plan limits are enforced on every call.