Fillout.io MCP Server
@MCP-Mirror
About Fillout.io MCP Server
Mirror of
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"danielma-tic_fillout-mcp-server": {
"command": "docker",
"args": [
"build",
"-t",
"mcp/fillout",
"."
]
}
}
}Tools
10`limit` (optional): Number of forms to return
Array of form objects
`formId` (string): Form identifier
Form details including questions and settings
`name` (string): Form name
Created form object
`formId` (string): Form identifier
Array of form responses
`formId` (string): Form identifier
Submission confirmation
Overview
What is Fillout.io MCP Server?
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.
How to use Fillout.io MCP Server?
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.
Key features of Fillout.io MCP Server
- 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
Use cases of Fillout.io MCP Server
- Automate form creation and management for customer feedback
- Collect and analyze survey responses programmatically
- Integrate form submission workflows into AI assistants
- Export and filter form data for reporting
FAQ from Fillout.io MCP Server
How do I get an API key?
Log in to your Fillout.io account, go to Account Settings → API & Webhooks, click "Create new API Key", and copy the key. Production keys start with fo_live_, test keys with fo_test_.
What are common authentication errors?
"Invalid API key provided" or "Authentication failed" indicates the key is missing, malformed, or invalid. "Test mode key used with live form" occurs when using a test key on a production form. "Rate limit exceeded" means too many requests; implement request throttling and check usage in the dashboard.
What are the runtime requirements?
Node.js 18 or later, and npm or yarn. Docker is optional for containerized deployment.
Where is data stored?
Data is stored on Fillout.io servers; the MCP server acts as a bridge and does not persist data locally.
How is authentication handled?
Authentication is via a Fillout.io API key passed as the FILLOUT_API_KEY environment variable. Keep the key secure, use test keys for development, rotate keys periodically, and never commit keys to version control.
More Other MCP servers
MCP Registry
modelcontextprotocolA community driven registry service for Model Context Protocol (MCP) servers.
Reactive Resume
amruthpillaiA one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
Inbox Zero AI
elie222The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.
Unity MCP ✨
justinpbarnettUnity MCP acts as a bridge between AI assistants and your Unity Editor. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.
Blender
ahujasidOpen-source MCP to use Blender with any LLM
Comments