Fillout MCP Server

Forms, questions, logic and submissions in your Fillout, worked by your agent.

เซิร์ฟเวอร์ MCP แบบโฮสต์

npx add-mcp 'https://cotlet.dev/mcp/v1/fillout'

ติดตั้งลง Claude Code, Codex, Cursor และอื่นๆ

เอกสาร

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Fillout API and MCP server: Let your AI agent build and close your Fillout forms.

Fillout has a REST API on every plan, Free included, with eight endpoints: list forms, read a form's questions, read, create and delete submissions, and add or remove webhooks (checked 27 Oct 2026). None of them creates or edits a form, its logic or its settings. Cotlet runs 15 Fillout tools hosted, over MCP for agents and REST for scripts, including the editor jobs.

Forms, questions, logic and submissions in your Fillout, worked by your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Fillout. Fillout is a trademark of its owner. If Fillout's own integrations cover what you need, use them first.

What can you automate in Fillout?

  • Build a form from a written brief
  • Add show and hide rules and page branches
  • Close a form on a date or a response cap
  • Change who gets the notification emails
  • Sum up this week's responses
  • Clear test and junk entries

Does Fillout have an MCP server or an API?

  • The Zite MCP, from Fillout's own company, says it in plain words: "creating or editing Fillout forms isn't supported over MCP. Use the form editor for those changes."
  • Form Agent builds fields, pages and logic, but only as a chat inside the editor, and "managing form level settings" such as close dates is not supported yet.
  • Zapier has 1 trigger (New Submission) and 1 action (Send Form); Make has only the trigger "Watch New Responses".
What you needFillout REST APIForm AgentCotlet
List forms and read responsesYes, 150 per callNot listedYes
Create a form with questionsNoIn the editor onlyYes
Show and hide rules, page branchesNoIn the editor onlyYes
Close, schedule or cap a formNoNot supported yetYes, after your OK
Notification recipients and publishingNoNoYes, after your OK
Called by your own agentYes, with a keyNo, it is a chat in FilloutYes, MCP or REST

Checked 27 Oct 2026. Sources: Fillout REST API (Fillout Help), Build forms with Form Agent (Fillout Help), MCP & Agents (Zite Help), Fillout Forms on Zapier, Fillout pricing

How does Cotlet connect to Fillout?

  1. Sign in to Fillout. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your Fillout password, and nothing respondents would see, from a publish to a closed form, goes live before you approve it.

Connect Fillout to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Sign in to Fillout in a Cloud Browser. Create a Cotlet account, open Fillout in its Cloud Browser, sign in with Google, Microsoft or your email (any plan, Free included) and press Enable for agents.
  2. Add the Cotlet address. Put https://cotlet.dev/mcp/v1 into your agent's MCP server or connector settings.
  3. Allow the connection. Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console instead.

https://cotlet.dev/mcp/v1 serves every app you enable on Cotlet, Fillout included. Enabled Fillout after connecting? Refresh the connector and its tools show up.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: fillout_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: fillout_write

How to use the Fillout REST API

Create your Cotlet API key

Create a Cotlet API key with access to Fillout and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Fillout in Cotlet and enable it for agents. Account access: Your own Fillout account (Google, Microsoft or email). What your agent can do follows your role: Admin, or Member, who edits only their own forms. You sign in in your own browser and keep your 2-step verification.

Make your first Fillout API request

REST:

curl https://cotlet.dev/api/v1/fillout/forms \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read forms and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "fillout",
  "tool": "list_forms",
  "result": {
    "forms": [
      {
        "form_id": "fpj3Kd9xQw2L",
        "name": "Webinar registration"
      },
      {
        "form_id": "rK8mTn4vYb1C",
        "name": "Discount application"
      },
      {
        "form_id": "tD6wNs3hLz8P",
        "name": "Autumn event"
      }
    ]
  }
}

Returns every form your account can see, each with the form ID and its name. Use form_id from each item as the form_id parameter of the other tools.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Fillout workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestSubmissions of a form with their answers, filtered by date, status or text. Use list_submissions in your configured workspace report.
MakeHTTP > Make a requestShow and hide rules on questions and the branches between pages. Use get_form_logic in your configured workspace report.
Python or Node.jsREST APIAccess settings and email notifications of a form. Use get_form_settings in your configured workspace report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Fillout; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Fillout API endpoints and MCP tools

Forms and questions

New forms start unpublished, and question edits stay in the draft until publish_form, so respondents see nothing half built. A Member edits only their own forms; an Admin reaches all of them.

  • List forms (list_forms, read): Forms in your Fillout account with their IDs and names.
  • Get form (get_form, read): A form's questions with ID and field type, plus calculations and URL parameters.
  • Create form (create_form, write): Create a new form with a name and its questions, not yet published.
  • Add question (add_question, write): Add one question of any field type to a form.
  • Update question (update_question, write): Change a question's label, type, options or whether it is required.

Logic

Rules use the same conditions as the editor's Add condition: an earlier answer or a URL parameter. Read the current logic first so a new rule does not fight an old one.

  • Get form logic (get_form_logic, read): Show and hide rules on questions and the branches between pages.
  • Set question logic (set_question_logic, write): Hide a question when conditions are met, or always.
  • Set page branch (set_page_branch, write): Route respondents from one page to another when a condition is met.

Access, notifications and publishing

These are the form-level settings Form Agent leaves to you. Each one changes what respondents or your team see at once, so all three writes ask first.

  • Get form settings (get_form_settings, read): Access settings and email notifications of a form.
  • Update form access (update_form_access, write, asks first): Close a form, set open and expiration dates, a submission limit or a closed message.
  • Set email notifications (set_email_notifications, write, asks first): Turn self-email notifications on a form on or off and set who gets them.
  • Publish form (publish_form, write, asks first): Publish a form so respondents can fill it in, with every change made since the last publish.

Submissions

Up to 150 per page, filtered by date, text or unfinished status. A deleted submission takes its file uploads with it.

  • List submissions (list_submissions, read): Submissions of a form with their answers, filtered by date, status or text.
  • Get submission (get_submission, read): One submission with all its answers, calculations and URL parameters.
  • Delete submission (delete_submission, write, asks first): Delete one submission permanently, with its uploaded files.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/fillout-api-mcp-server#tools

Who can see my Fillout session, and how do I revoke it?

  • What we store. Your signed-in Fillout profile, encrypted with AES-256-GCM, in Finland. Never the password.
  • What your agent gets. 15 Fillout tools. No cookie, no login, no Fillout API key.
  • What the session sees. What your Fillout user sees: an Admin reaches every form, a Member only their own.
  • What no tool touches. Billing, payments, integrations, team members, Zite apps and databases.
  • If Fillout signs you out. We email you a sign-in link. With 2FA on, you type the code once for the new browser.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.

Responses often hold names, emails and phone numbers of your respondents, and list_submissions passes them to your agent. Fillout's terms make you answerable for having consent to collect them, so read only the forms the job needs. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Approvals, undo and mistakes

  1. Builds a draft. create_form with one typed question per line of the brief. Nothing is public yet.
  2. Reads it back. get_form lists every question and type, and the agent fixes what does not match the brief.
  3. Waits for your OK. The publish waits in your Cotlet console, with where the responses will be saved.
  4. Sets the end. An expiration date or a response cap, also after your OK, so the form closes on time.
ActionUndo
Create a formDelete it from the dashboard; nobody saw the draft
Add or edit a question, set logicRestore an earlier version under the clock icon in the editor
Publish a formRestore the old version and publish again; respondents saw the new one meanwhile
Close a form or set datesReopen it; responses turned away while closed do not come back
Change notification recipientsSet the old list back; emails already sent stay sent
Delete a submissionNo undo; its file uploads go with it

4 of the 9 write tools ask first. create_form, add_question, update_question and the two logic tools run at once, because they change only the unpublished draft. Reads run at once. For a scheduled run you can switch the wait off per tool.

Fillout counts responses per calendar month in UTC, and preview test answers do not count. Ask your agent to test in Preview, not on the live link, and your cap stays intact.

MCP call:

{
  "name": "update_form_access",
  "arguments": {
    "form_id": "tD6wNs3hLz8P",
    "expiration_date": "2026-11-30T23:59:00+01:00",
    "closed_message": "Registration is closed. See you next year."
  }
}

REST:

curl -X PATCH https://cotlet.dev/api/v1/fillout/forms/tD6wNs3hLz8P/access \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"expiration_date":"2026-11-30T23:59:00+01:00","closed_message":"Registration is closed. See you next year."}'

Response:

{
  "form_id": "tD6wNs3hLz8P",
  "access": {
    "closed": false,
    "open_date": null,
    "expiration_date": "2026-11-30T23:59:00+01:00",
    "submission_limit": null,
    "closed_message": "Registration is closed. See you next year."
  }
}

A script that opens and closes event forms on a calendar can call the same tools over REST at /api/v1/fillout, with one key and one price. A call your Fillout role does not allow returns an error and costs nothing. Every tool row above lists its REST path.

How much does the Fillout MCP server cost?

About $14 a month for a small agency with 6 live client forms, 2,410 credits. Works on Fillout Free; Pro is $49 a month, or $40 billed yearly, with unlimited seats.

JobCallsCredits
Weekly summary of new responses, 5 forms6 × 4240
New form from a client brief5 × 4200
Show and hide rules on a form5 × 3150
Close a form on a date or a cap2 × 6120
Change who gets the notification emails2 × 240
Clear test and junk entries4 × 4160
Cloud Browser, 30 days1,500
Total2,410
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No Fillout API key, no Zite credits spent

The month is our example: 6 live forms, 4 new forms built from briefs, rules on 3 of them, 6 closings and a weekly response summary. Fillout publishes no typical account size; Pro allows 5,000 responses a month and Free 1,000. Dollars at the $29 pack rate.

Fillout MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
OfirOhan/fillout-mcp8 tools on the REST API: forms, submissions, imports, webhooks. MIT, 0 stars, last commit 4 Oct 2026.Needs your API key in a local file; no form building, logic or settings.
NoBanks/fillout-mcpThe same 8 operations in Python, with writes switched on by an env variable. MIT, 0 stars, last commit 31 May 2026.Same limits as the REST API.
mcpnexus-registry/fillout-mcp-serverLists "Create new forms" and "Update form settings" in its README. No license, last commit 6 Jan 2025.The API has no endpoints for those, so they cannot work.
Zapier MCP for FilloutNew Submission and Send Form, which emails a form link.Two operations; no reading past responses, no editing.

If your agent only needs to read responses and you are happy to run a server, a GitHub server on your API key does that for free. If you build in the editor yourself, Form Agent helps there. If your agent should build, rule, publish and close forms for you, Cotlet does that hosted.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Fillout tools go to contact@cotlet.dev.

Fillout API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Fillout under Integrations in the console and sign in to Fillout in its Cloud Browser. The trial starts when you sign up and needs no card.

How do I connect Fillout to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Fillout once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Fillout account through Cotlet, in their phone apps too.

What can ChatGPT do in Fillout?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Fillout: build a form from a brief; add branching logic to a form; close a form on a date or after a response limit. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need an API key or a paid Fillout plan?

No API key. Cotlet works in your signed-in Fillout account, so the key from Developer settings is not used. Fillout's help pages do not state which plan the REST API needs. What your agent can do follows your role: a Member edits only their own forms, and an Admin has full access to the workspace.

Can my agent edit a form while a teammate has it open?

Fillout says collaborators cannot edit the same form at the same time, but can edit different forms at once. Ask your agent to work on forms nobody has open, or on a duplicate.

Does Fillout have webhooks?

Yes. Each form can send its submissions to a webhook URL, and the API can add or remove one. They report new submissions only, not edits to the form. Your agent does not need them; to act on new responses, run it on a schedule.

What about forms moved into a Zite workspace?

After a form moves into a Zite workspace, only members of that workspace can edit it. Your agent can edit it when your own Fillout user is one of them.

Is the MCP server different from the REST API?

Only in how you call it. Both have the same 15 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts use REST.

Is Cotlet affiliated with Fillout?

No. Cotlet is independent and not affiliated with Fillout, Zite or Restly, Inc.

Can I use the Fillout API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.