⭐ Available in the following bundle: Core Bundle (incl. in all plans)
⭐ Available on the following plans: Basic, Pro, Agency, Business
👀 Not sure which plan you're on? Check your subscription here.
❗ The Heyflow MCP connector is new and still evolving. Features and details may change, and we'll keep this article up to date.
Once connected, you can build, analyse, and improve your funnels without leaving the conversation. You can:
Build and edit your funnels
Preview flows inline before they're created
Analyse and optimise using your live Heyflow data
Manage A/B tests end to end
Ask questions about your funnels, check analytics, and look up help articles
This article walks through what the connector can do, how to set it up, and what data your assistant receives when you use it.
What is MCP?
The Model Context Protocol is an open standard for connecting AI assistants to external services. It works like a browser extension, but for AI: once you authorize the Heyflow connector in your assistant, it can work with your Heyflow flows on demand while you chat.
What can you do?
Once the connector is set up, your assistant can build, analyse, optimise, and test your funnels — and answer questions using your Heyflow data and help center.
1. Build and edit your funnels
Describe the funnel you want, and your assistant builds it through Heyflow.
Your assistant can render a preview inline, so you see the flow in the chat and decide if you like it before anything is created.
Once you're happy, it creates the flow in your Heyflow workspace.
Ask for changes, and it edits the flow directly.
When it's ready, it can publish the flow for you.
Examples:
"Build a lead-gen funnel for my roofing business."
"Add a Phone Number Block to the second screen."
"Change the headline on my signup flow and publish it."
2. Analyse and optimise
Pull analytics for a specific funnel, including per-screen drop-off, and act on what you find in the same conversation.
"How is my 'onboarding' flow performing?"
"What's the conversion rate for flow abc123 this month?"
"Where are users dropping off on my signup flow?"
"How can I improve this flow?"
You'll see total visits, total submissions, conversion rate, and a screen-by-screen breakdown with drop-off percentages. Ask what to improve, and your assistant
suggests fixes grounded in Heyflow's benchmark data and best practice — and can make the edits directly.
3. Manage A/B tests
Plan and launch an A/B test from the chat, then analyse the results and optimise based on what wins.
"Set up an A/B test for two versions of my headline."
"Which variant is performing better?"
"Roll out the winner and publish."
💡 Put it on a schedule. Ask your assistant to review a flow each week, surface the biggest drop-offs, and test each suggested fix with an A/B test before you roll it out.
4. Look up your funnels
List the funnels you have access to in Heyflow and filter them by name.
"What funnels do I have?"
"Which of my funnels has the most responses?"
"Find my signup form."
For each funnel you'll see the ID, slug, title, response count, and whether it's published.
5. Heyflow Documentation and How-to's
Search the Heyflow help center from inside your assistant.
"How do I add a file upload field to my flow?"
"What integrations does Heyflow support?"
"How do I set up webhooks?"
"Can I use conditional logic across multiple screens?"
Your assistant answers with links back to the relevant help articles so you can read more if you need to.
❗ Setting up integrations isn't available through the connector yet. To connect a flow to your CRM or other tools, open it in the Heyflow app and add the integration there.
Set up
The Heyflow MCP server uses standard connection methods. Use the one your assistant supports.
HTTP + OAuth (recommended)
This method covers building, editing, analytics, and documentation.
Server URL:
https://mcp.heyflow.com/mcpTransport: HTTP
Authentication: OAuth 2.0
The exact setup steps depend on your assistant. Most MCP-compatible assistants have an Add MCP server option in their settings where you paste the URL and the client walks you through an OAuth login in your browser. Log in with your normal Heyflow credentials.
Once authorized, the assistant will show the Heyflow connector as connected and all three tools will be available.
Data sent when you connect
When you ask your assistant something that triggers a Heyflow tool, the connector sends the following to our servers:
Your identity. After you log in, your Heyflow user ID and email are included in the request so we can show you only your own funnels and analytics.
The question or filter. For example, your search query, the flow ID you asked about, or the date range.
A short log line for each tool call (tool name, user ID, result count) so our team can debug issues.
We do not send your assistant your individual responses. The assistant only sees what the tool returns in its reply, which is the same thing you'd see in the Heyflow app.
🔎 For the full details, including our third-party processors for this feature, see the Heyflow Privacy Policy.
Sign up through your assistant
Don't have a Heyflow account yet? You can sign up directly through your assistant. Just ask it to create a Heyflow account and follow the prompts to get connected.
Troubleshooting
The connector can't connect or the status is stuck on "needs authentication."
Open your assistant's MCP settings and re-authenticate the Heyflow entry. If that doesn't work, log out of Heyflow in your browser and try again.
You see "Access denied" for a specific flow.
You can only ask about funnels you own or have editor access to. Check that the flow ID belongs to your account.
You run out of Heyflow AI credits.
Building and editing through the connector uses your Heyflow AI credits. If you've run out, open the Heyflow app and navigate to the Plan section of the Account Settings to rectify this.
It looks like nothing is happening.
Ask your assistant for a status update — some builds and edits take a moment to complete. If it's still unresponsive, stop the request and start it again to give it a fresh connection.
💬 Questions, bug reports, or security concerns? Reach out to our team via the chat or [email protected]. Include the reference ID if your assistant showed you one. This helps us trace the request in our logs.