Fillout MCP connector
The Fillout connector brings your forms, submissions and webhooks into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can look up form responses and record new ones inside each person's own Fillout access.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me yesterday's submissions to the customer feedback form.
Working in Fillout with Elaichi
-
List all Fillout forms
-
Get single Fillout form by ID
-
Get single Fillout form submission by ID
How to connect Fillout to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Fillout MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Fillout through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Fillout is logged.
-
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.”
What connecting Fillout gets you
6 screens from Elaichi, each doing one job for your Fillout account.
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, Cursor or Microsoft Copilot
The agent
Ask about Fillout submissions in plain language.
Pull today's form responses, spot a pattern, get an answer from live Fillout records.
Copy the endpoint
AI apps
One endpoint puts Fillout in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared API key.
Tool catalog
8 Fillout tools, ready without writing code.
Forms, submissions and webhooks are covered from the first sign-in, no custom code.
Toolboxes
Every team gets its own Fillout toolbox.
Marketing sees lead forms, People sees applications, each toolbox scoped to one team.
Shared connections
Share a Fillout connection without sharing a key.
One person connects Fillout, teammates work through it and never see the API key.
Audit log
Every Fillout call is on the record.
When, who, what happened and which submission, kept in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Fillout digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Fillout
Queued
Workflows
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 health
Refreshed 4 minutes ago · every 15 minutes · from the forms collection
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%
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.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Fillout
All three can connect Fillout to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Fillout tools | Allow or restrict single Fillout tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Fillout call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 restricting the ability to delete a submission or remove a webhook. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Fillout?
Yes. Both let Claude, ChatGPT or Cursor use Fillout. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Fillout call.
How is Elaichi different from Composio for Fillout?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Fillout: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Fillout in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot