Connect your AI tools to FloeCopy link to this section
Two different things are called MCP in Floe, and this page is about one of them.
This page is Floe as an MCP server — you connect your own AI tool to Floe and work with Floe as a product: count demos, read what prospects asked, edit guides.
The other one is Floe as an MCP client — the Support Agent calling your MCP server to answer a signed-in user's account questions. That is documented under Support → Live account data with MCP. The two share a protocol and nothing else.
Floe exposes a remote Model Context Protocol server at:
https://api.floe.so/mcp
Any AI tool that speaks remote MCP over Streamable HTTP with OAuth can connect: Claude Code, Claude Desktop, claude.ai, ChatGPT and Cursor all do.
What you can do with itCopy link to this section
- Ask about your demos. How many demos last month, what prospects asked, what a specific session covered.
- Read what Floe knows about your product. The crawled content, the derived product knowledge, the guides the agent uses.
- Write guides. Rewrite what the Demo Agent says about a feature, in your words, from your editor.
Plan authoring — creating and editing the step-by-step flows the agent drives — is available to Floe staff accounts today. If you want it on your account, talk to us; it is a permission, not a rebuild.
Setting it upCopy link to this section
Claude CodeCopy link to this section
claude mcp add --transport http floe https://api.floe.so/mcp
Then run /mcp in Claude Code and follow the browser prompt. You will land on a
Floe consent screen, pick one organization, and approve the access you want.
Claude Desktop and claude.aiCopy link to this section
Add a custom connector in Settings → Connectors with the URL above. Claude opens the same consent screen in your browser.
On a Team or Enterprise plan, only Owners can add connectors. On the free plan you get one custom connector.
ChatGPTCopy link to this section
Add a connector with the URL above in Settings → Connectors. ChatGPT's connectors are tools-only — they do not surface the guided prompts described below, so use the walkthrough on this page instead.
CursorCopy link to this section
Add it to your MCP configuration with the URL above and "type": "http".
One organization per connectionCopy link to this section
A connection reaches exactly one organization. You choose which on the consent screen. If you work across two organizations, connect the tool twice — each connection is separate and separately revocable.
What a connection can doCopy link to this section
Access is spelled the same way as the permissions on your members page, and it can never exceed your own role. If you are a Member, a connection you make cannot read transcripts, because you cannot.
| Access | What it allows |
|---|---|
view_sites | Sites, demo readiness, demo metrics, guides |
update_sites | Writing Demo Agent guides |
view_content | Ingested content and product knowledge |
view_conversations | Demo sessions, conversations, full transcripts |
view_plans | Reading plans and their steps (staff accounts) |
manage_plans | Creating, editing and activating plans (staff accounts) |
view_conversations is Owner and Admin only, the same as in the dashboard —
a verbatim prospect transcript is a more sensitive read than a count.
Writing reference guides over a connection is not available yet, so no scope for it is offered.
The toolsCopy link to this section
Sites and demos — list_sites, get_site, get_demo_readiness,
get_demo_metrics
Prospect conversations — list_demo_sessions, get_demo_session,
get_transcript, top_questions, list_conversations, get_conversation
Guides — list_guides, get_guide, create_guide, update_guide
Product knowledge — list_content, get_content, get_product_knowledge
Plans (staff accounts) — reading, creating, editing, reordering and activating plans and their steps
Your tool only sees the tools your access covers, so the list you get may be shorter than this one.
There are no delete toolsCopy link to this section
Nothing here deletes or archives anything. Not a guide, not a plan, not a session. Deleting stays in the dashboard, where a human is looking at what they are about to remove.
Counting demosCopy link to this section
get_demo_metrics returns two numbers, both labelled, because Floe holds
two different definitions of "a demo" and they do not agree:
- Sessions started — demo sessions created in the window, including older sessions recorded before Floe labelled their source.
- People who took a demo — distinct people who reached the demo stage. Excludes those older sessions.
Neither excludes your own team's test runs, so if you have been demoing your own product to yourself, both numbers include it.
Writing a guideCopy link to this section
A guide is the script the Demo Agent follows for one plan. Rewriting one is the fastest way to change what the agent says.
Read the guide for the "reporting" topic on my site, then rewrite the
"what it does" section so it leads with the weekly summary rather than
the filters.
Two things to know before you do this.
Guides are checked on the way in. A guide that is too long, reads like marketing copy, or names a URL that does not exist on your product is rejected and not saved. You get the specific failure back, with the numbers.
- Plan guides cap at 6,000 characters; site-level guides at 4,000.
- Sentences average under 16 words, with under 15% over 30 words. The agent says this out loud.
- No marketing language — the rejection names the phrase it objected to.
- Every URL must match a page Floe has crawled. If your site has not been crawled yet the check cannot run, and the result tells you so — verify the links yourself when you see that.
Read floe://guide-contract from your tool for the full contract.
A hand-written guide is pinned. It stays exactly as you wrote it, and stops picking up improvements from re-crawls. There is no un-pin button today; ask us if you need one reverted.
Guided workflowsCopy link to this section
Claude Code and Claude Desktop surface Floe's prompts directly. In Claude Code
they appear as /mcp__floe__build_demo_walkthrough and
/mcp__floe__build_onboarding_plan, and they walk through the whole job —
what to read first, how to shape the arc, what order to write things in.
ChatGPT connectors do not support prompts. Paste the workflow from this page instead.
Revoking a connectionCopy link to this section
Organization settings → Connected apps lists every AI tool you have connected to that organization, what access each has, and when it was last used. Revoking one stops it working within a minute.
You see and revoke your own connections. A colleague's connection is theirs to revoke.
RelatedCopy link to this section
- Support Agent → Live account data with MCP — Floe as an MCP client, the other direction
- Security — what a connection can read, and how tokens are stored
- Product Insights — the same data in the dashboard