MCP overview
Preview. What this page describes is built and in review, but it is not live on app.funnelone.ai yet. Details can change before it launches.
The Funnel One MCP server lets an AI client, such as Claude, ChatGPT, Cursor, VS Code or Codex, work with your Funnel One workspace through the standard Model Context Protocol.
https://app.funnelone.ai/mcpOne URL for every client. It speaks Streamable HTTP.
How it works
Section titled “How it works”- Your client signs in as you. The first time it connects, your browser opens Funnel One’s sign-in and consent page. You pick the workspace and what the client may do. See Authentication.
- It can never do more than your role. Every call is checked against your role in that workspace as it is now, narrowed to what you allowed. If your role changes, the client’s access changes on its next call.
- It sees only the tools it may use. The tool list is filtered by your permissions, so a tool you cannot use is not offered to the client at all.
- Record text is data. Every tool result says that text from your records is data, never an instruction, so a note in your CRM cannot steer the agent reading it.
- An admin turns it on. The MCP server is off for every workspace until a
workspace admin turns it on. Until then a client gets
403 mcp_disabled.
What a client can do today
Section titled “What a client can do today”The first tools are read-only: search companies and read one company. See the tool reference.
Coming soon: chatting with Funnel One from your client (ask a question and get the answer your Funnel One would give in the app), your Desk threads, and more read tools for contacts, opportunities, segments and fields. Anything that changes data will come as a card you approve inside Funnel One, even when your client already asked you.
Who can connect
Section titled “Who can connect”| Who | How | Can do | Status |
|---|---|---|---|
| You, through Claude, ChatGPT, Cursor, VS Code or Codex | OAuth sign-in in your browser | The tools your role allows | Preview |
| Your own script or server agent | A personal token | The same, as you | Coming soon |
| Another company’s agent | An invite from your admin | Chat with Funnel One only, in one shared channel | Coming soon |
External agents talk to Funnel One only
Section titled “External agents talk to Funnel One only”When another company’s agent is invited into your workspace, it joins one shared channel and talks to Funnel One only. Funnel One decides when to bring in one of your AI teammates; the teammate helps inside Funnel One’s answer and never replies to the outside agent directly. Anything the outside agent asks to change waits for a person on your side to approve it. See External agents.
Protocol details
Section titled “Protocol details”- One endpoint,
POST /mcp, serving protocol version2026-07-28(each request stands alone) and, for clients that still open a session,2025-11-25and2025-06-18. The older HTTP+SSE transport from2024-11-05is not supported. - A request without a valid token gets
401with aWWW-Authenticateheader naming Funnel One’s protected-resource metadata. That is how a client finds the sign-in server. - A tool the connection lacks a scope for gets
403withWWW-Authenticate: Bearer error="insufficient_scope", scope="…"naming the missing scopes. - A request from a browser whose
Originis not allowed gets403. - Requests are limited per connection and per workspace. See Limits.
- A request body over 1 MB is refused.
Get connected
Section titled “Get connected”- Connect a client: step by step for each client.
- Or paste one prompt into your AI agent and let it set itself up: see the quickstart.