Typeform MCP Server: What It Does and How to Connect Typeform to AI in 2026
Yes — Typeform has an official MCP server. It’s a hosted, remote server at https://api.typeform.com/mcp that lets any MCP-compatible AI tool reach your Typeform account: read your forms, work with responses and contacts, and browse workspaces. So if you’re searching “Typeform MCP,” the connection you want does exist — with one honest caveat: Typeform describes it as a generally-available beta with limited capabilities, and the toolset is still expanding.
The thing worth knowing before you set it up: an MCP server hands Typeform to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your forms for you, nothing fires when a new response lands, and nothing runs while the chat is closed. Here’s exactly what the Typeform MCP does today, how to turn it on, where it stops — and what to use when you want Typeform work that runs on its own.
See also: the full MCP server list — which apps have one, and what each can reach.
What the Typeform MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, and others — talk to an outside app through a shared interface. Typeform maintains an official remote server that any MCP-compatible client can connect to. Because it’s a hosted endpoint, there’s nothing to install or run locally.
With it connected, an AI client can, within the beta’s current scope:
- List and inspect your forms — “show me the forms in my onboarding workspace” answered from the live account instead of a guess.
- Read and analyze responses — “summarize what people said in last week’s feedback form” grounded in the real submissions.
- Work with contacts — view, add, or update entries in your contacts list.
- Navigate workspaces and account details — pull the structure of what you’ve built.
Typeform is candid that this is early: the server started with read access to forms and read/write access to contacts, and more tools are landing over time. It’s genuinely useful for ad-hoc work — ask a question about a form’s results and get an answer grounded in your own data, without opening Typeform.
How to set up the Typeform MCP server
The remote server is the quick path — no code, no hosting:
- In your AI client’s connector settings, add a remote MCP server pointing at
https://api.typeform.com/mcp. (EU-data-center accounts usehttps://api.eu.typeform.com/mcpinstead.) - Authorize it against your Typeform account through the OAuth prompt — you’re granting the AI the scopes you approve.
- Confirm the tools appear in the client, then start a chat and ask it to list a form or read its responses.
The server uses the newer streamable HTTP transport, so make sure your client supports that. Because it’s beta, expect the exact tool list and setup details to shift as Typeform expands it — check Typeform’s own MCP developer docs for the current state before you rely on a specific capability.
Where the Typeform MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Typeform; it waits for you to ask.
- No triggers. A new response coming in, a form crossing a submission threshold, a specific answer that should route somewhere — none of these can start anything through MCP. There’s no “when this happens in Typeform, do that.”
- It’s one app at a time. The Typeform MCP knows Typeform. Getting a new response into your CRM, a Slack channel, and a spreadsheet means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens, refresh, and the blast radius of read/write access to your forms and contacts are all on you — and during the beta, the token can carry broad delete scope, so it’s worth watching what you grant.
So the Typeform MCP is a great way to ask about your forms and read results from a chat. It is not a way to make Typeform run — to have work happen on a schedule or in reaction to a new response, across the other tools a submission touches.
Running Typeform work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Typeform natively — no MCP server to host, no OAuth plumbing to maintain — and to the ~260 other apps it supports natively, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Typeform work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a new response comes in → qualify it, create or update the contact in your CRM, and post a summary to the
#leadsSlack channel — automatically, the moment it lands. - Every morning → summarize yesterday’s responses across your key forms and send the digest to the owner.
- When a response marks someone as interested → add a row to a Google Sheet, draft the first follow-up email for approval, and book a slot on your calendar.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Typeform connection and everything downstream.
If you just want to interrogate your forms from a chat, Typeform’s official MCP server is the right tool to try, beta and all. If you want Typeform to actually do things — on a new response, on a schedule, across every app a submission flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Typeform have an official MCP server?
Yes. Typeform ships a hosted, remote MCP server at https://api.typeform.com/mcp (with an EU endpoint at https://api.eu.typeform.com/mcp) that MCP-compatible AI clients can connect to. Typeform describes it as a generally-available beta with limited capabilities that are still expanding.
Is the Typeform MCP server free to connect? Connecting is free — you’re authorizing an AI client against your existing Typeform account and the scopes you approve. You still need whatever Typeform plan your forms live on, and standard API limits apply.
Can the Typeform MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Typeform work across apps — like reacting to every new response — you need a workflow tool like Carly rather than an MCP server.
Can I connect Typeform to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Typeform for you and lets you build the automation in plain language — describe what you want to happen and it wires up the form connection and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
