Skip to content

Fillout MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Read Fillout forms and submissions, export responses, and create submissions and webhooks.

Deletes · 3
CompareRegistry entry

9 tools: 3 can delete or cancel things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http fillout https://fillout.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

9 tools

Deletes or cancels 3Claude Code: deny
  • fillout_create_submissionsCreate up to 10 new submissions on a form, as if respondents had filled it in — e.g.No findings

    Why it is in this group

    • The name "fillout_create_submissions" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create up to 10 new submissions on a form, as if respondents had filled it in — e.g. to import responses collected elsewhere. Each submission needs its question answers (question ids from fillout_get_form); URL parameters, scheduling, payments, login email and timestamps are optional. Creates real records that trigger the form's integrations. Fillout: POST /forms/{formId}/submissions.

    Annotations the server declares

    • title: Create submissions
    • destructiveHint: true
  • fillout_create_webhookSubscribe a URL to a form's new submissions: Fillout will POST each submission (same shape as a fillout_list_submissions entry) to it.No findings

    Why it is in this group

    • The name "fillout_create_webhook" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Subscribe a URL to a form's new submissions: Fillout will POST each submission (same shape as a fillout_list_submissions entry) to it. Returns the webhook id — keep it, it is the only handle for removing the webhook later. Fillout: POST /webhook/create.

    Annotations the server declares

    • title: Create a submission webhook
    • destructiveHint: true
  • fillout_remove_webhookStop a webhook from receiving submissions.No findings

    Why it is in this group

    • The name "fillout_remove_webhook" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Stop a webhook from receiving submissions. Recoverable: create it again with fillout_create_webhook (it gets a new id). Fillout: POST /webhook/delete.

    Annotations the server declares

    • title: Remove a submission webhook
    • destructiveHint: true
Only reads 6Claude Code: allow
  • fillout_count_submissionsCount a form's submissions matching the same filters as fillout_list_submissions (date range, status, search) without pulling the answers — e.g.No findings

    Why it is in this group

    • The name "fillout_count_submissions" says "count": a word for reading.
    Description, as the server wrote it
    Count a form's submissions matching the same filters as fillout_list_submissions (date range, status, search) without pulling the answers — e.g. 'how many responses this week?' or 'how many partial submissions?'. Reads totalResponses from GET /forms/{formId}/submissions with limit=1.

    Annotations the server declares

    • title: Count submissions
    • readOnlyHint: true
  • fillout_export_submissionsFetch many submissions in one call by walking the offset pagination (150 per page, paced under Fillout's 5 requests/second limit), up to max_submissions.No findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.
    Description, as the server wrote it
    Fetch many submissions in one call by walking the offset pagination (150 per page, paced under Fillout's 5 requests/second limit), up to max_submissions. Same filters as fillout_list_submissions. Use this for analysis across a whole response set; the result says whether it was truncated. Fillout: GET /forms/{formId}/submissions (repeated).

    Annotations the server declares

    • title: Export submissions
    • readOnlyHint: true
  • fillout_get_formFetch one form's metadata: every question (id, name, type), calculations, URL parameters, scheduling and payment fields, and quiz settings.No findings

    Why it is in this group

    • The name "fillout_get_form" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one form's metadata: every question (id, name, type), calculations, URL parameters, scheduling and payment fields, and quiz settings. Use the question ids to read answers or to create submissions. Fillout: GET /forms/{formId}.

    Annotations the server declares

    • title: Get form questions and metadata
    • readOnlyHint: true
  • fillout_get_submissionFetch a single submission by id, with every answer.No findings

    Why it is in this group

    • The name "fillout_get_submission" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single submission by id, with every answer. Fillout: GET /forms/{formId}/submissions/{submissionId}.

    Annotations the server declares

    • title: Get one submission
    • readOnlyHint: true
  • fillout_list_formsList every form in the Fillout account — each form's name and formId.No findings

    Why it is in this group

    • The name "fillout_list_forms" says "list": a word for reading.
    Description, as the server wrote it
    List every form in the Fillout account — each form's name and formId. Start here to find the formId the other tools need. Fillout: GET /forms.

    Annotations the server declares

    • title: List forms
    • readOnlyHint: true
  • fillout_list_submissionsList one page of a form's submissions (answers to every question, calculations, URL parameters, scheduling, payments, quiz score, login email), filtered by date range, status or fr…No findings

    Why it is in this group

    • The name "fillout_list_submissions" says "list": a word for reading.
    Description, as the server wrote it
    List one page of a form's submissions (answers to every question, calculations, URL parameters, scheduling, payments, quiz score, login email), filtered by date range, status or free-text search. Offset pagination: the response carries totalResponses and pageCount. Fillout: GET /forms/{formId}/submissions.

    Annotations the server declares

    • title: List submissions
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http fillout https://fillout.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fillout__fillout_list_forms",
      "mcp__fillout__fillout_get_form",
      "mcp__fillout__fillout_list_submissions",
      "mcp__fillout__fillout_get_submission",
      "mcp__fillout__fillout_count_submissions",
      "mcp__fillout__fillout_export_submissions"
    ],
    "ask": [],
    "deny": [
      "mcp__fillout__fillout_create_submissions",
      "mcp__fillout__fillout_create_webhook",
      "mcp__fillout__fillout_remove_webhook"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as fillout. Review it before you use it.