Skip to main content
Glama
Sign In
Fillout MCP Server

Fillout MCP Server

by OfirOhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Fillout MCP Server

CI MCP License: MIT

A Model Context Protocol server for Fillout. It lets Claude, Cursor, ChatGPT and other AI agents work with your forms and submissions.

Unofficial. This is a community project and is not affiliated with Fillout. It was built from Fillout's public REST API docs.

What you can ask your agent

  • "Summarize this week's responses to my Customer feedback form and group the complaints by theme."

  • "Which leads from the Demo request form mentioned a budget over $10k? Put them in a table."

  • "Import these 8 rows from my CSV into the Event signup form."

  • "Set up a webhook so new Applications go to https://hooks.example.com/apply."

Related MCP server: Formswrite MCP

Tools

Tool

What it does

Writes?

list_forms

List all forms (name + id)

No

get_form

Questions, types, calculations, URL params, quiz/payment fields

No

list_submissions

Filter by date range, status, free-text search; paginated; compact output

No

get_submission

One submission by id

No

create_submissions

Create 1–10 submissions (imports, back-fills)

Yes

delete_submission

Permanently delete a submission

Destructive

create_webhook

Send new submissions to a URL

Yes

delete_webhook

Remove a webhook

Yes

Submissions are returned in a compact, token-friendly shape: answers are keyed by question name, and empty fields are dropped. Pass raw: true to get Fillout's full objects instead. Destructive tools carry MCP destructiveHint annotations, so clients can ask before running them.

Setup

  1. Create an API key in Fillout: Settings → Developer → API key.

  2. Build it:

git clone https://github.com/OfirOhan/fillout-mcp.git
cd fillout-mcp && npm install && npm run build

Claude Desktop

Add this to claude_desktop_config.json:

{
  "mcpServers": {
    "fillout": {
      "command": "node",
      "args": ["/absolute/path/to/fillout-mcp/dist/index.js"],
      "env": { "FILLOUT_API_KEY": "your_api_key" }
    }
  }
}

Cursor / Claude Code / other MCP clients

Use the same command, node /path/to/fillout-mcp/dist/index.js, with FILLOUT_API_KEY in the environment. For Claude Code:

claude mcp add fillout -e FILLOUT_API_KEY=your_api_key -- node /path/to/fillout-mcp/dist/index.js

Configuration

Variable

Default

Notes

FILLOUT_API_KEY

(required)

Fillout API key

FILLOUT_REGION

us

Set to eu for EU-hosted accounts

FILLOUT_BASE_URL

(from region)

Override for self-hosted instances

Development

npm install
npm test   # builds, runs unit tests and an end-to-end MCP stdio test against a fake Fillout API

The tests run on Node 20, 22 and 24 in CI.

Notes & limits

  • Fillout's API limits requests to 5 per second per key.

  • Submissions created via the API don't trigger Fillout notifications, workflows or integrations. This is Fillout's behaviour.

Author

Built by Ofir Ohana, an AI agents engineer. Issues and PRs are welcome.

License

MIT

Available Tools

8 tools
create_submissionsCreate submissionsA

Create 1-10 submissions for a form (for example, to import data). Call get_form first to get question ids. Note: submissions created via the API do not trigger Fillout notifications, workflows or integrations.

Inputs: formId (required), submissions (required).

create_webhookCreate webhookA

Register a URL that Fillout calls on every new submission to a form. Returns the webhook id.

Inputs: url (required), formId (required).

delete_submissionDelete submissionA
Destructive

Permanently delete a submission. This cannot be undone, so confirm with the user first.

Inputs: formId (required), submissionId (required).

delete_webhookDelete webhookB
Destructive

Remove a webhook by its id.

Inputs: webhookId (required).

get_formGet form structureA
Read-only

Get a form's questions (id, name, type) plus calculations, URL parameters, scheduling, payment and quiz fields. Use the question ids when creating submissions.

Inputs: formId (required).

get_submissionGet submissionC
Read-only

Get one submission by ID.

Inputs: formId (required), submissionId (required), raw, includeEditLink.

list_formsList formsA
Read-only

List all Fillout forms in the account (name and formId).

Inputs: no named parameters.

list_submissionsList submissionsA
Read-only

Query a form's submissions with date range, status, text search and pagination. Returns compact records (answers keyed by question name) unless raw=true.

Inputs: formId (required), raw, sort, limit, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Tools cleanly separate into three resources: forms (list_forms, get_form), submissions (get_submission, list_submissions, create_submissions, delete_submission), and webhooks (create_webhook, delete_webhook). Each tool has a distinct resource+action pairing with no meaningful overlap.

    Naming Consistency5/5

    Every tool follows a strict verb_noun snake_case pattern (list_forms, get_form, create_submissions, delete_webhook, etc.). The convention is applied uniformly across all resources with no deviations.

    Tool Count5/5

    Eight tools is well-scoped for a forms/submissions/webhooks domain, with each tool earning its place. No redundant or filler tools are present.

    Completeness4/5

    Submission lifecycle is well covered (create, get, list, delete) and webhooks have create/delete, but there is no list_webhooks to discover existing webhooks, and no form create/update (arguably out of scope for an API). These are minor gaps an agent can mostly work around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Filly Forms MCP Server

      eneopt
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes the Filly Forms REST API as MCP tools for AI agents, enabling form type listing, record CRUD, data preview, and document upload with AI extraction.
      MIT