Fillout.io MCP Server
About
The Fillout.io MCP Server is a Model Context Protocol server that integrates with the Fillout.io API to enable form management, response handling, and analytics. It is designed for developers and AI assistants to programmatically create, retrieve, and submit forms and responses.
Details
- Author
- MCP-Mirror
- Downloads
- 245
- Categories
- Other
Jump to
- List all forms and get form details
- Create, delete, and update forms
- Submit and retrieve form responses
- Filter and export response data
- Retrieve analytics like response rates and completion times
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Fillout.io MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Set up the server with Claude Desktop using either Docker or NPX configuration, providing your Fillout.io API key as the FILLOUT_API_KEY environment variable. Obtain an API key from your Fillout.io account settings; production keys start with fo_live_ and test keys with fo_test_. The server exposes tools such as list_forms, get_form, create_form, get_form_responses, and submit_form_response.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"fillout.io mcp server": {
"danielma-tic_fillout-mcp-server": {
"command": "docker",
"args": [
"build",
"-t",
"mcp/fillout",
"."
]
}
}
}
}
McpServers
{
"danielma-tic_fillout-mcp-server": {
"command": "docker",
"args": [
"build",
"-t",
"mcp/fillout",
"."
]
}
}
Fillout.io MCP Server
MCP Server for the Fillout.io API, enabling form management, response handling, and analytics.
Token Setup
1. Get your Fillout.io API Key:
- Log in to your Fillout.io account
- Go to Account Settings → API & Webhooks
- Click "Create new API Key"
- Copy your new API key
2. API Key Information:
- Production keys start with fo_live_
- Test keys start with fo_test_
- Test keys only work with test forms
- API keys provide access to all resources in your account
3. Replace your-fillout-api-key in the configuration with your API key.
⚠️ Security Notes:
- Keep your API key secure and private
- Use test keys for development
- Store keys in environment variables
- Rotate keys periodically
- Never commit keys to version control
Token Troubleshooting
Common Error Messages
1. "Invalid API key provided" or "Authentication failed"
- Cause: API key is missing, malformed, or invalid
- Solution:
- Verify key starts with fo_live_ or fo_test_
- Check for extra spaces or characters
- Ensure environment variable is set correctly
- Create a new key if necessary
2. "Test mode key used with live form"
- Cause: Using test key (fo_test_) with production form
- Solution:
- Use live key for production forms
- Create test form for development
- Switch to appropriate key type
3. "Rate limit exceeded"
- Cause: Too many API requests
- Solution:
- Implement request throttling
- Check usage in dashboard
- Optimize request patterns
Validation Steps
1. Check API Key Format:
# Key should:
- Start with 'fo_live_' or 'fo_test_'
- Be approximately 50 characters
- Contain only letters, numbers, and underscores
2. Test API Key:
curl -H "Authorization: Bearer your-api-key" \
https://api.fillout.com/v1/api/forms
Features
Form Management
- List all forms - Get form details - Create new forms - Delete forms - Update form settingsResponse Handling
- Submit form responses - Get form submissions - Filter responses - Export responsesAnalytics
- Response rates - Completion times - Submission trendsTools
1. list_forms
- Get all accessible forms
- Parameters:
- limit (optional): Number of forms to return
- offset (optional): Pagination offset
- Returns: Array of form objects
2. get_form
- Get detailed form information
- Parameters:
- formId (string): Form identifier
- Returns: Form details including questions and settings
3. create_form
- Create a new form
- Parameters:
- name (string): Form name
- description (optional string): Form description
- questions (array): Array of question objects
- type: Question type (e.g., 'ShortAnswer', 'MultipleChoice')
- name: Question text
- required: Whether question is required
- choices: Array of choices for multiple choice questions
- Returns: Created form object
4. get_form_responses
- Get form submissions
- Parameters:
- formId (string): Form identifier
- filters (optional): Response filters
- pageSize (optional): Results per page
- afterDate (optional): Filter by submission date
- beforeDate (optional): Filter by submission date
- status (optional): Filter by completion status
- Returns: Array of form responses
5. submit_form_response
- Submit a new response
- Parameters:
- formId (string): Form identifier
- responses (array): Array of answers
- questionId: Question identifier
- value: Response value
- calculations (optional): Custom calculations
- Returns: Submission confirmation
Setup
Usage with Claude Desktop
Docker Configuration
{
"mcpServers": {
"fillout": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"FILLOUT_API_KEY",
"mcp/fillout"
],
"env": {
"FILLOUT_API_KEY": "your-fillout-api-key"
}
}
}
}
NPX Configuration
{
"mcpServers": {
"fillout": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-fillout"
],
"env": {
"FILLOUT_API_KEY": "your-fillout-api-key"
}
}
}
}
Building
Prerequisites
- Node.js 18 or later - npm or yarn - Docker (optional)Local Development
```bashSign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



