BioFlow / MCP
BioFlow ships a remote MCP (Model Context Protocol) server. Any MCP-capable agent — Claude, Claude Code, ChatGPT, Copilot, MCP Inspector, or your own — can read your analytics, edit your bio page drafts, and (with your explicit say-so) publish, all through OAuth you grant and can revoke in one click.
Streamable HTTP, no local install and no API keys to copy around:
https://app.getbioflow.com/api/mcpAdd BioFlow from your terminal, then sign in when prompted:
claude mcp add --transport http bioflow https://app.getbioflow.com/api/mcpClaude web and desktop (as a custom connector), ChatGPT, Copilot, MCP Inspector — the setup guide has the exact steps for each, plus the OAuth discovery endpoints if you are building your own client.
Read pages, analytics, contacts and files; create and edit drafts; publish. Every workspace operation is guarded by a single OAuth scope, and an agent only ever sees the workspaces you chose when you connected it — one, several, or all of them, including any you join later.
The server uses Code Mode: your assistant sees two tools, search_tools and execute_typescript, and reaches these operations through them, with the same scope checks.
Every connection starts on a consent screen listing each requested scope in plain language. Revoke any app in Settings → Connected AI apps — its next request is refused, even if its access token has not expired. The same screen shows how many tool calls each app has made and when it last ran.
Block edits wait in the draft; title, description and theme edits apply to your live page without waiting for a publish. The publish-class tools are disabled per workspace until you flip an explicit settings toggle, and even then every publish is a two-step confirm — the first call only ever returns a preview.
Draft writes are guarded by optimistic concurrency, so a stale edit is refused rather than overwriting newer work, and writes take an idempotency key so a retried call can't run twice.
Every refusal is a typed code an agent can act on — a missing scope, a disabled dangerous operation (with a deep link to the setting), a plan limit, a stale draft. No mystery errors, no silent no-ops. Full denial reference →
Yes. Agents connect through OAuth 2.1 — you approve exactly which scopes an app gets on a consent screen, a connection reaches only the workspaces you choose there, and every tool call is written to an audit log, with each app's call count and last-used date shown on the Connected AI apps page. You can revoke an app at any time, and its next request is refused.
Only what its granted scopes allow. With write access it can edit your blocks, which wait in the draft until you publish, and your page's title, description and theme, which apply to your live page without waiting for a publish. Every publish, delete and other destructive action is a two-step flow: the agent gets a preview and a short-lived confirm token first, and nothing commits until a second call with that token.
Ask your assistant to run revoke_connected_app, or revoke the app from your BioFlow Connected AI apps page. Its next request to your workspace is refused, even if the access token it holds has not expired, and its refresh token is revoked, so it can't get new access.
No. The MCP server is included on every plan, including Free. Tool calls ride your plan's existing limits — an agent can't spend more than your plan allows, and over-limit calls get a structured QUOTA_EXCEEDED response instead of silent failure.
Yes. On the consent screen you choose which workspaces a connection covers, or all of them, which also covers workspaces you join later. An agent should call workspace.list to see them, and when a connection covers more than one, each tool call names its workspace with workspaceId.
Any MCP client that speaks Streamable HTTP with OAuth: Claude (web and desktop, as a custom connector), Claude Code, ChatGPT, Microsoft Copilot, MCP Inspector, and any agent framework with an MCP client. Registration is dynamic — no pre-shared API keys needed.
Setting it up: the MCP setup guide. More on BioFlow itself: the full FAQ, the integration directory, and pricing.
Sign up free, connect any MCP client, and let it keep your page fresh. MCP access is included on every plan.