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 tool is guarded by a single OAuth scope, and tokens are scoped to one workspace — an agent only ever sees the workspace you connected it to.
Every connection starts on a consent screen listing each requested scope in plain language. Revoke any app in Settings → Connected AI apps — revocation is instant, and the same screen shows a full audit trail of every tool call the app ever made.
Draft edits never touch your live page. 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, tokens are limited to one workspace, and every tool call is written to an audit trail you can review in Settings → Connected AI apps. You can revoke an app at any time and revocation is instant.
Only what its granted scopes allow — and nothing that touches your live page. Draft edits stay drafts. Publishing and scheduling are off by default per workspace, and even after you enable them, every publish 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.
Open Settings → Connected AI apps in your BioFlow dashboard and revoke the app. Revocation is instant — its access and refresh tokens stop working immediately.
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.
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.