Fillout MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILLOUT_REGION | No | Set to eu for EU-hosted accounts. | us |
| FILLOUT_API_KEY | Yes | Fillout API key. Create it in Fillout under Settings → Developer → API key. | |
| FILLOUT_BASE_URL | No | Override the base URL for self-hosted instances. Defaults based on FILLOUT_REGION. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_formsA | List all Fillout forms in the account (name and formId). |
| get_formA | Get a form's questions (id, name, type) plus calculations, URL parameters, scheduling, payment and quiz fields. Use the question ids when creating submissions. |
| list_submissionsA | Query a form's submissions with date range, status, text search and pagination. Returns compact records (answers keyed by question name) unless raw=true. |
| get_submissionC | Get one submission by ID. |
| create_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. |
| delete_submissionA | Permanently delete a submission. This cannot be undone, so confirm with the user first. |
| create_webhookA | Register a URL that Fillout calls on every new submission to a form. Returns the webhook id. |
| delete_webhookB | Remove a webhook by its id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
Eight tools is well-scoped for a forms/submissions/webhooks domain, with each tool earning its place. No redundant or filler tools are present.
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.