Host an MCP server for external AI clients.
An MCP host turns what you already built on FlowFn — platform actions, data sheets, workflows, and agents — into tools any Model Context Protocol client can call. Pick what to expose, hand out one endpoint and a rotatable token, and Claude Desktop, Cursor, or your own AI app can use them. You bring the tools; FlowFn runs the server.
New form submission
Contact form · 12 today
Classify intent
gpt-4o-mini · returns category
Slack · Post to #sales
Routes pricing leads to sales
One URL, one token, a catalog of tools.
Create an MCP, tick the workflows, agents, data sheets, and platform actions it may expose, and FlowFn publishes a standards-compliant endpoint. Paste the URL and token into any MCP client config and your tools appear in its tool list — no gateway to run, no protocol code to write, nothing to scale.
New form submission
Contact form · 12 today
Classify intent
gpt-4o-mini · returns category
Slack · Post to #sales
Routes pricing leads to sales
Everything you built, callable by AI.
One catalog, four sources
Expose platform actions, data-sheet reads, workflows, and agents as MCP tools from a single host. Each becomes a typed, described tool an AI client can discover and call — no adapters per source.
One endpoint, rotatable token
Every MCP gets its own URL and a bearer token you can rotate or revoke at any time. Rotate and the old token stops working instantly — no redeploy, no client changes beyond pasting the new value.
Deny-by-default eligibility
Nothing is exposed until you choose it, and platform tools only appear when an admin flags them for the MCP host. Secured data-sheet columns are never returned. What the AI cannot see, it cannot call.
Standards-compliant, stateless
Built on the official Model Context Protocol SDK over streamable HTTP, stateless per request. It speaks the same protocol as Claude Desktop, Cursor, and every other MCP client — no bespoke integration on either side.
Per-call credits by plan
Each tool call debits credits at a plan-based rate, metered on your credit ledger as an "MCP tool call" line. Downstream workflow, agent, and AI usage bills as it always has — no surprise multipliers.
Rate-limited + moderated
The host enforces per-plan call limits and runs the same moderation your other public surfaces do, so an over-eager client can't run up your bill or push unsafe input into your automations.
This is the server side. Your agents can also be the client.
Two directions, one protocol. An MCP host exposes your FlowFn tools outward so external AI clients can call them. Separately, a FlowFn agent can be an MCP client — reaching out to someone else's MCP server via mcp connections.
This page is about hosting. You decide exactly which workflows, agents, sheets, and platform actions a host publishes; the token holder gets that catalog and nothing more. Change the selection and the tool list updates on the next connect — no new endpoint, no new token.
New form submission
Contact form · 12 today
Classify intent
gpt-4o-mini · returns category
Slack · Post to #sales
Routes pricing leads to sales
Expose a sheet without exposing everything in it.
A data sheet you expose becomes a read tool — the AI client can query rows, but secured columns never leave FlowFn and write access is never implied. Workflows and agents run with their own configured auth, so an MCP call can't escalate past what the automation itself is allowed to do.
Every call lands in the activity feed and the credit ledger, so you can see which client called which tool, when, and what it cost. Rotate the token the moment a client should no longer have access.
match_8f3a
6 players · live
wss://stream.flowfn.com
Rex
gg — rematch?
Ana
one more, winner keeps the crown
server
match.ended · score 3:2 → channel events
workflow Leaderboard Sync started → reply on “events”
NPC Goblin
You dare return? The crown stays with me.
streaming agent replied on “ai” — this room remembers the match
Channels
state
players
chat
players
events
server → workflow
ai
FlowFn-only · NPC
Give any AI client your backend, safely.
Your team in Claude Desktop / Cursor
Point your team's AI assistant at an MCP host and it can run your internal workflows, look up records in a data sheet, and trigger agents — all from chat, with a token you control and can revoke.
Ship an AI integration to customers
Hand a customer an endpoint and a scoped token instead of building and documenting a bespoke API. They connect their own MCP-capable AI and get exactly the tools you exposed.
Agent-to-agent tool sharing
Expose a curated set of workflows and agents so partner or downstream AI systems can call them as tools — deny-by-default, per-call metered, and auditable in the activity feed.
Automations behind a standard protocol
Wrap the workflows and platform actions you already run into a Model Context Protocol surface any current or future MCP client understands — without maintaining protocol code yourself.
MCP hosting is included on eligible plans.
Higher plans unlock MCP hosts with plan-based tool limits and per-call credit rates. What you expose and the tokens you issue stay intact across plan changes.
Turn your FlowFn account into an AI toolbox.
Create an MCP, pick the tools it exposes, and paste the endpoint into your AI client in minutes. The server, the protocol, the auth, and the metering are already running.
We’re here to help you ship
Email sales for volume pricing and enterprise procurement, reach support for everything else, or drop us a message and we’ll get back to you.
Talk to sales
Volume pricing, security review, and enterprise procurement — email us and we’ll get back fast.
General inquiries
support@flowfn.com
Prefer not to open your mail client?