Skip to main content
FlowFn
IntegrationsTemplatesPricingDocsBlogSign inStart free
All documentation

v4.0.0

UpdatedJul 4, 2026Reading time1 min read

Released 2026-07-04. Host your own MCP server — a new top-level feature alongside Workflows, Agents, and Streams.

New

  • MCP servers. Create an MCP, attach the platform-tool actions, data sheets, workflows, and agents you want to expose, and get a token-authed endpoint that external AI clients (Claude Desktop, Cursor, the MCP Inspector) connect to. They can list and call exactly what you attached — nothing else.
  • Rotatable connection token. Each MCP has a single bearer token you copy into your client's config. Rotate it any time from the editor — the old token stops working immediately, on the next request.
  • Copy-ready client config. The editor shows the endpoint URL and a ready-to-paste client configuration snippet, so connecting a new client is copy-and-go.
  • Safe by default. Sensitive platform tools are never exposed unless an admin explicitly enables them for the MCP surface; data-sheet password/secured columns are never returned; and every tool call is metered against a per-day plan limit. Exposing a workflow or agent is flagged as high-privilege, since a client can then trigger everything it does.

This is FlowFn hosting an MCP server (the opposite of an agent calling an external MCP server, which already existed).

Spotted an issue or have feedback?

support@flowfn.com
Back to docs hub →