Typeform MCP vs dForms: What Your Claude Agent Can Actually Do With Each (2026)

The Typeform MCP server lets Claude work inside your Typeform account, and the dForms connector lets Claude work inside dForms. Both are real, both connect from the same Claude menu, and both let your agent create and publish a form from a chat. So the useful question is not "which one has MCP". It is what your agent can actually finish with each one, and what happens when the answers start coming in.

This guide compares the two tool by tool. Every claim about Typeform comes from Typeform's own pages, linked, and checked on November 11, 2026: the developer docs for its MCP server, the supported tools list, the help article on using Typeform from Claude and the pricing page. The dForms side comes from the dForms connector docs, checked the same day.

What the Typeform MCP server does

Typeform describes its server as a way to reach forms, pages, automations, contacts and response analytics from an AI client, without building against each REST endpoint. In Claude, it ships as a connector in the Connectors Directory. Behind the scenes, the help center says, that connector is powered by the MCP server.

The tool groups

According to the tools page, the tools come in six groups, named by prefix:

• Forms: create an empty form, edit it through patches, preview it, publish it, duplicate it and delete it.
• Insights: counts, averages, NPS, rankings, time series, and responses listed one row per respondent.
• Pages: build and publish Typeform Pages, including custom domain routes.
• Themes: create and update form and page themes.
• Automations: email, webhook, delay and integration steps that run after a submission.
• Contacts: a contacts database with lists and form field mapping.

How a form gets built

Editing is ordered. Your agent first creates an empty form. Then it validates a batch of changes, applies them to a draft with the token it got back, and only then publishes. The docs say publishing should happen only "when the user explicitly wants the form to go live". In addition, Claude lets you set each tool to Always allow, Needs approval or Blocked when you connect.

What it does not do yet

Typeform keeps an honest "not yet supported" list. As of today it includes response deletion and bulk response export, legacy form webhooks, retrieving embed codes, and moving forms between workspaces. For those, the docs point you back to the REST API. Also, the tools list has no tool to go back to a previously published version of a form.

Plans still apply

Every account sees the same tool list. However, the plans page explains that access to each feature depends on your subscription and is checked when a tool runs. So a publish call can fail with a payment error if the form uses a feature your plan lacks. The response limits apply too: Typeform's plan guide lists 10 responses a month on Free, 100 on Basic, 1,000 on Plus and 10,000 on Business.

What the dForms MCP does

dForms is the form builder for AI agents: the one your agent actually wants to use. The connector lives at https://mcp.dforms.ai/mcp, and you sign in with your own dForms account. There is no API key to create or store, and any member of a workspace can connect.

According to the connector docs, your agent can:

• Build forms: create a form from a plain description, edit it as a draft, publish it, go back to the version that was live before, discard unpublished changes, duplicate it and delete it.
• Score answers: points live on the answer options, so every response arrives with its score. You can then list responses filtered by date, status or score.
• Read results: read one response in full, open uploaded files, export to CSV and delete responses.
• Check analytics: views, starts, completions and drop off by step.
• Route leads: choose where responses go (webhooks or HubSpot) and see which Calendly events a form can book.

Also, publishing, reverting and deleting are marked as destructive. So before any of them runs, your agent tells you what will change and waits for your yes.

Two more facts matter for this comparison. First, dForms is free, and responses are not counted or billed. Second, it is open source under the MIT license, so you can self-host it.

Typeform MCP vs dForms side by side

Here is the comparison in one table. The Typeform column cites Typeform's pages, checked November 11, 2026.

The short version: Typeform's server is broader, because it also covers Pages, themes, contacts and automations. On the other hand, the dForms connector is narrower and built around one loop: build the form, publish it, score it, route it.

Setup in Claude: both connectors step by step

Both take about a minute. You can keep both connected and turn each one on or off per chat.

Connect the Typeform MCP in Claude

From the Typeform help article, checked today:

1. In Claude, open Customize in the sidebar and select Connectors.
2. Click Add, then Browse connectors, and search for Typeform.
3. Click Connect, log in to Typeform and click Authorize.
4. Review the tool permissions and choose Always allow, Needs approval or Blocked for each group.

If Claude shows no tools after connecting, Typeform suggests opening the connector and choosing Refresh tools list. Personal access tokens are not supported. Accounts on EU data centers add it as a custom connector with an EU server URL instead.

Connect dForms in Claude

From the dForms connector docs:

1. Open dForms on the web once, at app.dforms.ai, with the account you will connect. That sign-in links your workspaces.
2. In Claude, click + in the chat box, then Connectors, Add connector, Add custom connector.
3. Name it dForms, paste https://mcp.dforms.ai/mcp and click Add.
4. Enter your email and the 6 digit code dForms sends you. Then ask: List my forms in dForms.

The full walkthrough, with Claude Code, Cursor and ChatGPT, is in our guide to create a form with Claude.

How your agent builds a scored form in dForms

This is the part a side by side table cannot show. With dForms connected, one message gets you a form with scoring and routing, as a draft you can check first.

Paste this into Claude and change the details:

Create a form in dForms called "Inbound lead check".
Questions: name, work email, company size (1 to 10 / 11 to 50 / 51 to 200 / 200+),
budget this year (none / under 10k / 10k to 50k / over 50k),
and what they want to solve (open text).
Points: company size 51 to 200 = 10, 11 to 50 = 6, others = 2.
Budget over 50k = 10, 10k to 50k = 7, under 10k = 3, none = 0.
Show the booking step only when the total is 70% or more.
Send every response to HubSpot. Leave it as a draft and give me the preview link.

Your agent builds the questions, the points and the logic, then returns the draft link. When you say "publish it", it confirms and goes live. A week later, ask it to "list responses at 70% or more, sorted by score", and it does. The scoring model behind that prompt is explained in the guide to a form with scoring, and the HubSpot side in connect a form to HubSpot.

Running a script or a server side agent instead of Claude? Then use an API key from the Developers page. Keys allow 120 calls a minute. They have no per key scopes and no approval step, so an agent with a key can publish directly. If you want to review forms first, ask it to leave them in draft.

Which one to pick for your agent

Pick by where your forms live and what your agent has to finish.

Stay on the Typeform MCP if your team already lives in Typeform, pays for a plan that covers the features you use, and wants the agent to also manage Pages, themes or the contacts database. Its tool list is wide, and Typeform documents it carefully.

Pick dForms if the agent is the main user and the job is lead or candidate intake. You get scoring on every answer, a revert after publish, delete and CSV over the connector, and no response meter. That matters most for a hiring round or a campaign that might bring in 2,000 answers.

Use both if you are migrating. Keep the Typeform connector on for old forms, and let the agent build new ones in dForms. The Typeform alternative guide covers what to check before you move.

Either way, the Typeform MCP and dForms share one idea: the form builder should be something your agent can drive. The difference is how much of the loop your agent can close on its own. If you want to see the agent side of the product first, start at dForms.

Frequently asked questions

Is Typeform's MCP server free?

Typeform's server connects to any Typeform account, but what it can do depends on your plan. Typeform checks each feature when a tool runs, and its plan guide lists 10 responses a month on the Free plan. dForms is free, with responses not counted or billed.

Does Typeform's MCP connector work with Claude?

Yes. Typeform lists a native connector in Claude's Connectors Directory, authorized with OAuth. Its help center also lists ChatGPT and any client that supports custom MCP connectors.

Is dForms the only MCP form builder?

No. Typeform, Tally and Jotform also ship MCP servers. dForms differs in what the agent can finish: scoring per answer, routing to a calendar or CRM, revert after publish, free unlimited responses and self-hosting.

Can my agent publish a form without asking me?

Through the dForms connector, no: publish is marked destructive, so the agent asks first. Typeform's docs tell connectors to publish only when the user explicitly asks, and Claude lets you set its tools to Needs approval. With a dForms API key, an agent can publish directly.

Can I move my Typeform forms to dForms with my agent?

Yes, as a rebuild. Ask Claude to read a form through the Typeform connector, then create the same questions in dForms as a draft. Check the draft, then publish it.

Can I self-host dForms?

Yes. dForms is open source under the MIT license, so you can run it on your own infrastructure.