Create a Form With Claude: Connector Setup Step by Step (2026)

You can create a form with Claude in one message, without opening a form builder, as long as Claude has somewhere to build it. Claude itself does not host forms. What it can do is use a connector: a small bridge to an app that does. Add the dForms connector once. From then on, "make me a lead form with three questions" becomes a form with a public link, scored answers and a path to your calendar.

This guide walks through the setup in four steps. Then it shows the prompt, what happens when you publish, and how to read the answers without leaving the chat. It applies to claude.ai, Claude Desktop and Cowork, with a short section for Claude Code, Cursor and ChatGPT at the end.

Everything below comes from the dForms connector documentation and Claude's help article on custom connectors, checked on October 28, 2026.

What you need before you create a form with Claude

Three things, and none of them is an API key.

• A dForms account, opened on the web at least once. Go to dForms, sign in, and open your workspace. That sign-in is what links the workspace to the connector. If you signed in before October 23, 2026, log out and sign in again once.
• A Claude plan that allows custom connectors. According to Claude's help center, custom connectors using remote MCP are available on Free, Pro, Max, Team and Enterprise plans. Free users are limited to one custom connector. On Team and Enterprise plans, only owners can add connectors for the organization.
• Nothing to install. The connector is a URL. Claude connects to it from Anthropic's cloud, so it works the same in the browser, the desktop app and the mobile apps.

The connector signs you in with your own dForms account. So every form Claude builds belongs to you, in your workspace, with your role. What you cannot do in the dashboard, Claude cannot do either.

Step 1: Add the dForms connector in Claude

Four clicks and one email code.

1. In Claude, click the + button in the chat box, then Connectors, Add connector, Add custom connector. You can also get there from Settings and then Connectors.
2. Use dForms as the name and paste this URL. Leave the advanced settings empty and click Add.

https://mcp.dforms.ai/mcp

3. Your browser opens the dForms sign-in page. Enter your email and type the 6 digit code dForms sends you. Back in Claude, dForms shows as Connected.
4. Open a new chat and ask: List my forms in dForms. If Claude lists them, you are set. If you belong to several workspaces, Claude asks which one to use; answer with the name, and say "switch to" another one whenever you need.

Connectors can be turned on or off per conversation from the same + button, so you decide in which chats Claude can touch your forms.

If Claude says it is signed in but refused

That means dForms has not linked that sign-in to a workspace yet. Open app.dforms.ai with the same account, make sure you have an active workspace, and connect again. A workspace you have not opened on the web in the last 30 days is not reachable until you open it.

Step 2: Create a form with Claude in one message

Now describe the form the way you would describe it to a colleague. The more specific the request, the less you edit afterwards. Say what the form is for, the questions, the answer options, which answers deserve points, and what should happen at the end.

Copy this prompt and change the details:

Create a form in dForms called "Demo request".
Questions: full name, work email, company website,
team size (just me / 2 to 10 / 11 to 50 / 51 to 200 / 200+),
what they want to automate (open text),
and when they want to start (this month / this quarter / later).
Points: team size 11 to 200 = 10, 2 to 10 = 5, others = 2;
start this month = 10, this quarter = 6, later = 1;
open answer that names a concrete process = 10, vague = 3, blank = 0.
Show the calendar booking step at the end only when the total is 70% or more.
Apply my brand kit. Leave it as a draft and give me the preview link.

That is all it takes to create a form with Claude. It builds the questions, the options with their points, the logic and the ending from the description. It applies your workspace's logo, colors and fonts if you have a brand kit. Then it returns the link to the draft.

A few things worth knowing about what Claude can do here, from the connector's own list of 49 tools:

• Forms: create from a description, edit as a draft, publish, go back to the version that was live before, discard unpublished changes, duplicate, delete, and change the end of the link.
• Responses: list with filters by date, status or score, read one in full, export to CSV, see how answers to each question add up.
• Analytics: views, starts, completions and drop off by step.
• Integrations: choose where a form's responses go (webhooks or HubSpot) and send a test to a webhook. Connecting HubSpot or Calendly in the first place stays in the dashboard.

Want a deeper look at what an agent needs from a form builder? Read the AI form generator guide.

Step 3: Review the draft, then publish

Open the preview link and answer the form once yourself. Check the order, the wording, the logic and the ending. If something is off, tell Claude in plain words: "make the team size question required" or "move the email question to the start". Every edit stays in the draft; your public link, if the form was already live, keeps showing the published version.

When it looks right, say publish it. Publishing replaces what is live, so the connector marks it as a destructive action. Claude tells you exactly what will change and waits for your yes before it runs. The same goes for deleting a form or a response, reverting, discarding a draft, or applying the brand kit to a form.

After publishing, the form is live at a link of the shape app.dforms.ai/{your account code}/f/{form slug}. Ask Claude to change the end of the link, or to give you the embed snippet for your site. If you need to undo, ask it to go back to the version that was live before.

Step 4: Read the answers and act on them

Once responses arrive, every one carries its score. Ask for them from the chat:

List this week's responses to "Demo request" sorted by score.
For every response at 70% or more, give me one line on why it looks like a fit,
and export the full list to CSV.

Claude lists the responses with their scores, summarizes the top ones and hands you the CSV. Because you set the booking step to show only for 70% or more, the hot ones already picked a time on your calendar. The rest can go to HubSpot or to a webhook; ask Claude to set the form's destinations and it does.

This is the same scoring model as the 25 question lead qualification template. Hand Claude that template as the spec, and you create a form with Claude in one message.

Claude Code, Cursor and ChatGPT use the same connector

The server URL is the same for every app. Only the way you add it changes.

Prefer an API key for a script or a server side agent? dForms has those too, created on the Developers page, with 120 calls a minute per key. The connector is the recommended path for a person working with Claude, because there is nothing to copy or store.

Create a form with Claude without losing control

Handing a form builder to an agent raises fair questions. Here is how the connector answers them.

• Your role applies. Claude acts as you, with your role in that workspace. A member cannot change the brand kit or the notification emails through Claude, because a member cannot do that in the dashboard either.
• Changes that replace or delete ask first. Publish, revert, discard, delete and brand kit changes are marked destructive; Claude explains what will change and waits for your yes.
• Drafts are private. Edits live in a draft until published. Your public link only changes when you say publish, and a published form can be reverted.
• What is logged. For each call, dForms records the time, who called, the tool name and the ids of the forms it touched. Not the form content, not the answers. The privacy page lists it in full.
• Writes are rate limited per person and per workspace. If Claude reports "too many writes", wait a moment and ask again.

dForms is free with unlimited responses and open source under the MIT license. So the cost of letting Claude build your next form is one conversation. If Typeform is where your forms live today, the Typeform alternative guide covers what to check before moving them.

Frequently asked questions

Can I create a Google Form with Claude?

Not directly: Claude has no built in Google Forms tool, and Google Forms has no official MCP connector. If you want to create a form with Claude that it can also publish and score, use a form builder with a connector, like dForms. Then share the public link or embed it on your site.

Does the Claude connector for forms need an API key?

No. The dForms connector signs you in with your own account through OAuth the first time Claude calls it. There is nothing to create, copy or store. API keys exist for scripts and server side agents, and they are managed on the Developers page.

Does the Claude MCP form connector work on the free Claude plan?

Yes. According to Claude's help center, custom connectors using remote MCP are available on the Free plan, limited to one custom connector. Pro, Max, Team and Enterprise plans allow more.

Can Claude publish a form without asking me?

Through the connector, no. Publishing replaces what is live, so it is marked destructive, and Claude tells you what will change and waits for your yes. Through an API key, an agent can publish directly, so ask it to leave forms in draft if you want to approve them.

What if I have several dForms workspaces?

Claude asks which one to use the first time, and every answer says which workspace it used. Say "switch to" followed by the workspace name to change.

Is creating forms with Claude free in dForms?

Yes. dForms is free, responses are not counted or billed, and the project is MIT licensed, so you can also self-host it.