Can my team share one Fillout connection?

Yes. One person connects Fillout with an API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who pulled a submission, not the person who connected Fillout.

Survey

Fillout MCP connector

The Fillout connector brings your forms, submissions and webhooks into Elaichi, so Claude, ChatGPT, Cursor or the Elaichi Agent can look up form responses and record new ones inside each person's own Fillout access.

Connect on Elaichi How to connect

How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
One address. https://api.elaichi.ai/mcp, the same for every user.
Their own access. An agent never gets more than the person it acts for.

8 tools

How to connect

How to connect Fillout to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Fillout once

Open Connections, choose Add connection, and pick Fillout.
Optionally set Share with to give a team access, then press Connect.
Paste a Fillout API key. One person generates a token in Fillout and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

fillout

All categories

Fillout

Alchemer

Canny

Google Forms

Prodege

SafetyCulture

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Fillout MCP connector for Claude

1

Open Customize, then Connectors.
2

Press Add.
3

Name it, paste the MCP server URL, then Continue.

https://api.elaichi.ai/mcp
4

Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Fillout MCP connector for ChatGPT

1

Open Plugins, then press the + button.
2

Name it and paste the endpoint into Server URL.

https://api.elaichi.ai/mcp
3

Leave Authentication on OAuth, then tick the risk acknowledgement.
4

Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Fillout MCP connector for Cursor

1

Open ~/.cursor/mcp.json.
2

Add the endpoint under mcpServers.

https://api.elaichi.ai/mcp
3

Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Fillout to any MCP client

1

Add the endpoint as a remote MCP server.

https://api.elaichi.ai/mcp
2

Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Fillout on Elaichi See pricing

Use cases

What teams do with Fillout through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

Marketing

Review this week's lead form submissions

Ask which lead capture forms filled up this week and pull the newest submissions to hand to sales. The answer comes from live Fillout records, not a spreadsheet export.
Support

Read customer feedback without opening Fillout

Pull the latest responses to your feedback survey and ask what customers keep mentioning. Every submission stays tied to the form it came from.
People

Pull a job application on demand

Fetch a single application submission by its ID when a hiring manager asks about a candidate. No hunting through the Fillout dashboard.
Operations

Log an intake request on someone's behalf

When a request arrives by phone or email, have the agent create the submission on the right Fillout intake form so nothing lives only in an inbox.
Product

Summarize research survey responses

List every submission to a research survey and ask for the themes. Scan hundreds of open text answers in the time it takes to read one.
Events

Check registrations before the doors open

Count how many people registered through the event form and pull the latest sign-ups. Remove a duplicate registration submission when someone registered twice.

Try asking

“Show me yesterday's submissions to the customer feedback form.”
“Which of our Fillout forms got the most submissions this week?”
“Pull the latest submission from the job application form.”

See all 8 Fillout tools below

AI tools

Fillout tools for your AI agents

8 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fillout, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Fillout gets you

6 screens from the product, each doing one job for your Fillout account.

The agent

Ask about Fillout submissions in plain language.

Pull today's form responses, spot a pattern, get an answer from live Fillout records.

forms
submissions
webhooks
answers

Ask Elaichi to work across your apps.

Show me yesterday's submissions to the customer feedback form.

Which of our Fillout forms got the most submissions this week?

Pull the latest submission from the job application form.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint puts Fillout in every client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emma Laurent	• Connected	4 minutes ago
Cursor	S Sofia Ricci	• Connected	2 hours ago
ChatGPT	C Clara Nowak	• Connected	Yesterday

Tool catalog

8 Fillout tools, ready without writing code.

Forms, submissions and webhooks are covered from the first sign-in, no custom code.

List all Fillout forms
Get single Fillout form by ID
Create a Fillout form submission
Delete a Fillout form submission by ID

ElaichiTools

Tool	Action	Description
List all Fillout forms	List	List all forms in your Fillout account. Returns each form's id and formId (the form's public ID).
Get single Fillout form by ID	Get	Get a single Fillout form's metadata by id, including all the questions in that form. Returns: id, name, questions, calculations, urlParameters, scheduling, payments, quiz, formId. Required: id.
Create a Fillout form submission	Create	Create new submissions for a Fillout form. Returns the created submissions including their submissionId and, where applicable, an editLink, with form-specific content. Required: form_id, submissions.
Delete a Fillout form submission by ID	Delete	Delete a submission of a Fillout form by id. Returns an empty 204 response on success. Required: id, form_id.
Get single Fillout form submission by ID	Get	Get a single submission of a Fillout form by id. Returns the submission record including its submissionId and an editLink when includeEditLink is true, with form-specific content. Required: id, form_id.

Toolboxes

Every team gets its own Fillout toolbox.

Marketing sees lead forms, People sees applications, each toolbox scoped to one team.

Marketing
Support
People
Operations

ElaichiToolboxes

Name	Source template	Tools	Created
Marketing toolbox Fillout · lead capture forms	Fillout starter	18	Mar 4, 2026
Support toolbox Fillout · feedback surveys	—	9	Mar 2, 2026
People toolbox Fillout · applications and onboarding forms	—	24	Feb 27, 2026
Operations toolbox Fillout · intake requests	Fillout starter	6	Feb 19, 2026
Product toolbox Fillout · research surveys	—	31	Jan 30, 2026
Events toolbox Fillout · registration forms	—	12	Jan 22, 2026

Shared connections

Share a Fillout connection without sharing a key.

One person connects Fillout, teammates work through it and never see the API key.

Marketing
Support
People Ops
Operations

ElaichiConnections

Connection	Scope	Status	Access
FI Fillout (Marketing) Connected by Emma Laurent	Personal	• Active	1 team · 6 members
FI Fillout (Support) Connected by James Whitfield	Organization	• Active	3 teams · 24 members
FI Fillout (People Ops) Connected by Sofia Ricci	Organization	• Active	2 teams · 11 members
FI Fillout (Operations) Connected by Daniel Ortega	Personal	• Needs re-auth	1 team · 3 members
FI Fillout (Product Research) Connected by Clara Nowak	Personal	• Active	Not shared
FI Fillout (Events) Connected by Michael Brennan	Personal	• Active	2 teams · 9 members

Audit log

Every Fillout call is on the record.

When, who, what happened and which submission, kept in an append-only log.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emma Laurent [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J James Whitfield [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	S Sofia Ricci [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	D Daniel Ortega [email protected]	Fillout Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	C Clara Nowak [email protected]	Fillout Forms Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	M Michael Brennan [email protected]	Fillout Forms List	Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Fillout submissions into a digest.

New submissions are fetched, grouped and drafted into a summary a person approves before it posts.

Fillout digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

Run now

✓

Schedule

Every weekday at 08:00

0.2s
✓

Fetch forms

Fillout

1.4s
✓

Group by owner

Transform

0.1s
✓

Draft the digest

Agent step

Ran with 4 tools, returned a structured summary

6.2s
Approve the digest

Needs approval

Assigned to Michael Brennan

Approve Deny
Post the digest

Fillout

Queued

Collections and dashboards

Fillout form health, computed without a model.

Submissions per day across 14 days, four metrics and a team breakdown, refreshed on schedule.

Fillout health

Refreshed 4 minutes ago · every 15 minutes · from the forms collection

Live

Forms

1,284 ↓ 12%

Submissions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Forms created

Last 14 days

By team

Share of activity

Marketing 34%

Support 27%

People Ops 21%

Operations 18%

Related connectors

More from the catalog

Browse all 450+ connectors →

FAQ

Frequently asked questions

How do I connect Fillout to Claude?

Connect Fillout in Elaichi first: Fillout connects with an API key, so you copy the key from your Fillout settings and paste it into Elaichi. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the address. Sign in to Elaichi when Claude asks and Fillout is ready.

Does Fillout work with ChatGPT and Cursor as well as Claude?

Yes. Once Fillout is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Fillout once and every client picks it up.

What can an AI agent actually do with my Fillout data?

With Fillout connected, an agent can list your forms, open a specific form, list the submissions it has received, pull a single submission, record a new submission on your behalf, or delete a submission. It can also set up or remove a webhook so other tools hear about new responses. Short, concrete asks such as "latest five submissions to the feedback form" work better than long paragraphs.

Does connecting Fillout give the AI every form in my workspace?

An agent only sees the Fillout forms and submissions that the connected API key can already reach, because every call runs inside that person's own access. Elaichi can narrow that further, for example limiting a team to reading submissions and nothing else, but it never widens what Fillout itself allows.

Can I stop an agent from deleting or changing things in Fillout?

Yes. Restrictions in Elaichi work per action, so you can allow reading Fillout forms and submissions while blocking the ability to delete a submission or remove a webhook. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.

What happens to a Fillout connection when someone leaves?

Offboarding the person in Elaichi ends their access to Fillout through every client at once. If they had shared a Fillout connection with a team, it keeps working for everyone else. Disconnecting Fillout once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Fillout MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Fillout is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Put Fillout in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Fillout Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.