Connectors · Marketing & media
Fillout MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Fillout and the rest of your systems. It gives your agent 8 Fillout actions (4 reads, 2 writes and 2 that wait for a confirmation) and holds the Fillout credential itself, so the agent never does. It paces Fillout's limits and records every call.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "fillout.forms.list", intent: "check which Fillout account is connected"}# Get all forms · read · 1 upstream call- 8actionsin one signed file
- 4readlook, never change
- 2writecreate and update
- 2wait for a yesdestructive, confirmed first
Set up
Connect Fillout in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Fillout.
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
api_keyFillout API keyhostWhere your Fillout lives: your host
account { op: "connections.requirements", service: "fillout" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "fillout.forms.list" }# get all forms · read · 1 upstream callcheck { action: "fillout.submissions.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Fillout at a glance
- Sign-in
- Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
- You provide
api_key- Setup fields
host- Limits we pace to
- 5 calls a second, per connection
- API covered
- Fillout REST API v1 (OpenAPI 1.0.0), at your Fillout instance's API base URL, which you enter when connecting
- Built from
- Fillout's documentation, read 23 October 2026fillout.comfillout.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 4 of 4 reads, for up to 2 minutes; a write clears what it affects
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Fillout.
8 actions in 3 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 4readlook, never change
- 2writecreate and update
- 2destructivewait for a confirmation
Submissions
42 read · 1 write · 1 destructive
Get all submissions · Create submissions · Get submission by ID · Delete submission by ID
Forms
22 read · 0 write · 0 destructive
Get all forms · Get form metadata
Webhooks
20 read · 1 write · 1 destructive
Create a webhook · Remove a webhook
Top actions
The Fillout API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 8 of Fillout's 8 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
fillout.forms.listGet all forms | Get all forms. | read | content.form.list36 connectors |
fillout.submissions.listGet all submissions | Get all submissions. | read | content.form_response.list20 connectors |
fillout.forms.getGet form metadata | Get form metadata. | read | content.form.get35 connectors |
fillout.submissions.createCreate submissions | Create submissions. | write | content.form_response.create9 connectors |
fillout.webhooks.createCreate a webhook | Create a webhook. | write | automation.webhook.create209 connectors |
fillout.webhooks.deleteRemove a webhook | Remove a webhook. | destructive | automation.webhook.delete211 connectors |
Try it
Prompts to paste into Claude.
Each one names the Fillout actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Get all forms in Fillout and tell me what stands out.
calls
fillout.forms.list - Writewrite
Create submissions in Fillout. Show me exactly what you will send before you save it.
calls
fillout.submissions.create
Governance for Fillout
Destructive actions wait for a yes.
2 Fillout actions are destructive. These are all of them:
- Delete submission by ID
fillout.submissions.delete - Remove a webhook
fillout.webhooks.delete
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Delete submission by ID?
intent: the user asked me to delete submission by ID
account { op: "keys.create", name: "fillout-agent", allowed_actions: ["fillout.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "fillout.submissions.delete", approver: "[email protected]" }, { match: "fillout.webhooks.delete", approver: "[email protected]" } ]}Cost
What Fillout costs on actionlake.
Every Fillout action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Fillout refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 8 Fillout actions
- 1actions pageeach page of a long list is one call
- 4reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Fillout action.
8 actions by area: the id your agent calls, what it does, and its effect.
Submissions4
fillout.submissions.createCreate submissionswritefillout.submissions.deleteDelete submission by IDdestructivefillout.submissions.getGet submission by IDreadfillout.submissions.listGet all submissionsread
Forms2
fillout.forms.getGet form metadatareadfillout.forms.listGet all formsread
Webhooks2
fillout.webhooks.createCreate a webhookwritefillout.webhooks.deleteRemove a webhookdestructive
Questions
The Fillout MCP server, answered.
Is there a Fillout MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 8 Fillout actions across submissions, forms and webhooks, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Fillout.
What do I need to connect Fillout?
Fillout API key. Plus your host. The free call account { op: "connections.requirements", service: "fillout" } lists exactly what to paste.
Can an AI agent delete or change things in Fillout?
Only if its key allows it, and only with an explicit confirmation. 2 Fillout actions are destructive, including delete submission by ID and remove a webhook. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Fillout API limit?
actionlake paces every call to the limits in the Fillout service file: 5 calls a second per connection. Repeated reads are answered from cache (4 Fillout actions can be), which never reaches Fillout.
What does a Fillout action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (1 Fillout actions page). Cache hits, searches, dry runs and calls Fillout refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Fillout API does it cover?
The Fillout REST API v1 (OpenAPI 1.0.0) at your Fillout instance's API base URL, which you enter when connecting. It is built from Fillout's documentation as read on 23 October 2026. 8 actions in 3 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my Fillout data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 2 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Fillout credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Fillout today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.
