otherapi_key

Fillout Forms

Fillout is a platform that allows users to create and manage forms, offering a REST API for programmatic access to form data.

Verdict

The Fillout Forms MCP lets your team manage form workflows without leaving Switchy. @mention it to list all forms in your account, kick off OAuth flows for embedded form apps, or revoke tokens when users sign out. Most useful for product and support teams who embed Fillout forms in their own tools and need to script authorization or audit which forms exist. Requires a Fillout API key. The MCP doesn't retrieve form responses or create new forms — it handles auth orchestration and form inventory only.

Common use cases

  • Audit which forms are live in production
  • Generate OAuth consent URLs for embedded forms
  • Revoke user tokens on sign-out events
  • Script form access checks before deployment
  • Inventory forms across multiple workspaces

Integration

Vendor
Fillout Forms
Category
other
Auth
API_KEY
Tools
3
Composio slug
fillout_forms

Tools

  • Authorize OAuth

    Tool to initiate the oauth authorization process for third-party applications. use when you need to generate the url to redirect your users to the fillout consent page.

  • Get forms

    Tool to retrieve a list of all forms in your account. use when you need to list your forms after authenticating with fillout.

  • Invalidate Access Token

    Tool to revoke an existing oauth access token. use when the user logs out or you need to programmatically invalidate a token after deauthorization. example: "invalidate token abcdefg123456". this endpoint does not return a json body. succes

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP' and search for Fillout Forms. 3. You'll be prompted to paste your Fillout API key — find this in your Fillout account under Settings > API. 4. Grant the MCP access to your workspace by clicking 'Connect'. 5. Open any Space and type '@Fillout' to confirm the connection is live. 6. Test it by asking '@Fillout list all my forms' — you should see a JSON response with form IDs and titles. 7. To invoke OAuth flows or invalidate tokens, reference the specific tool in your prompt (e.g. '@Fillout generate an OAuth URL for my app').

What teammates see: by default, memories from Fillout Forms are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List All Forms

@Fillout list all forms in my account and show me their titles and IDs
Open in a Space →

Generate OAuth URL

@Fillout generate an OAuth authorization URL for my application with redirect URI https://myapp.com/callback
Open in a Space →

Revoke Access Token

@Fillout invalidate the access token abc123xyz456 for the user who just signed out
Open in a Space →

Check Form Inventory

@Fillout show me a count of all forms and flag any with duplicate titles
Open in a Space →

Prepare OAuth Integration

@Fillout explain the OAuth flow and generate a test authorization URL I can use in staging
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Fillout list all my forms and show me which ones have been published in the last 30 days

Output

Based on your Fillout account, you have 12 forms total. Of these, 4 were published in the last 30 days: 'Q1 Customer Feedback Survey' (published 5 days ago, 47 responses), 'Event Registration - March Webinar' (published 12 days ago, 203 responses), 'Employee Onboarding Checklist v2' (published 18 days ago, 8 responses), and 'Product Feature Request Form' (published 26 days ago, 31 responses). The remaining 8 forms are older or currently in draft status.

Notes

This example demonstrates the 'Get forms' tool's ability to retrieve your form inventory. The MCP returns metadata like creation dates and response counts, which the AI can filter and summarize. Requires a valid API key with read access to your Fillout workspace.

Prompt

@Fillout I need to revoke access for token tk_prod_8x9y2z after our contractor's engagement ended

Output

Access token 'tk_prod_8x9y2z' has been successfully invalidated in your Fillout account. This token can no longer be used to access forms or submission data. Any applications or integrations using this token will immediately lose access and will need to re-authenticate if access should be restored in the future.

Notes

This showcases the 'Invalidate Access Token' tool for security hygiene when team members leave or integrations are deprecated. This is a destructive action—once revoked, the token cannot be restored. Useful for programmatic offboarding workflows in Spaces where multiple tools need cleanup.

Prompt

@Fillout generate an OAuth authorization URL so our new CRM integration can access form submissions

Output

Here's your OAuth authorization URL: https://fillout.com/oauth/authorize?client_id=your_client_id&redirect_uri=https://your-app.com/callback&response_type=code&scope=forms:read submissions:read. Direct your users to this URL to grant the CRM integration access to form data. After they approve, Fillout will redirect to your callback URL with an authorization code you can exchange for an access token.

Notes

This example uses the 'Authorize OAuth' tool to set up third-party integrations. The MCP generates the consent page URL but doesn't complete the OAuth flow—you'll need to handle the callback and token exchange in your application. Useful when building Spaces that connect Fillout data to other services.

Use-case deep-dives

Customer onboarding form handoff

When Fillout beats building your own intake flow

A 6-person SaaS team runs customer onboarding through Fillout forms embedded in their product. The support lead wants the AI to pull form submissions during weekly check-ins to spot drop-off patterns. This MCP works if your forms are already live in Fillout and you need read access to submission data or form metadata. The three-tool scope is narrow—you can list forms and manage OAuth tokens, but you can't read submission responses or update form logic through this MCP. If your workflow is 'show me this week's incomplete onboarding forms,' you'll need Fillout's submissions API separately. Use this MCP when your team already runs forms in Fillout and needs the AI to coordinate OAuth handshakes or enumerate form IDs for downstream automation.

Event registration multi-tool sync

Fillout as the front door to a larger workflow

A 3-person nonprofit uses Fillout for event registration, then syncs responses into Airtable and sends confirmation emails via SendGrid. The ops manager wants the AI to kick off that chain when a new form goes live. This MCP handles the OAuth setup and form-list retrieval, so the AI can confirm which Fillout form to watch, but it stops there—no submission webhooks, no response parsing. If your workflow is 'when someone submits form X, do Y,' this MCP gets you the form ID but you'll script the rest outside Switchy. It's the right call when Fillout is one spoke in a hub-and-spoke integration and you need the AI to manage the OAuth dance or audit which forms exist before handing off to Zapier or Make.

Agency client form audit

When you manage Fillout accounts for multiple clients

A 4-person marketing agency builds lead-gen forms in Fillout for 12 clients. The account director wants the AI to generate a weekly report listing all active forms per client to catch stale campaigns. This MCP is built for that: the 'Get forms' tool pulls the full form inventory after OAuth, and the token-invalidation tool cleans up when a client engagement ends. The limitation is you can't inspect form fields or submission counts—just names and IDs. If your audit needs to include 'forms with zero submissions this month,' you'll hit the API separately. Use this MCP when your team juggles multiple Fillout accounts and needs the AI to maintain an up-to-date form catalog without manually logging into each client dashboard.

Frequently asked

What does the Fillout Forms MCP do in Switchy?

It lets AI agents list your Fillout forms, kick off OAuth flows for third-party apps, and revoke tokens when users log out. You'd use this if you're building workflows that need to know which forms exist or manage OAuth sessions programmatically. It doesn't create forms or pull submission data — just handles auth and form inventory.

Do I need admin access to connect Fillout Forms?

You need an API key from your Fillout account, which typically requires admin or owner permissions to generate. The MCP also includes OAuth tools, so if you're letting end users authorize their own Fillout accounts through your workflow, they'll go through Fillout's consent screen. Check your Fillout plan to confirm API access is enabled.

Can the Fillout MCP submit responses or export form data?

No. The three tools focus on OAuth management and listing forms. If you need to pull submission data or programmatically fill out forms, you'll have to call Fillout's REST API directly or use a different integration. This MCP is for auth flows and form discovery, not data extraction.

Why use this MCP instead of Fillout's API directly?

The MCP wraps OAuth token lifecycle and form listing into tool calls your AI agent can invoke conversationally. If you're already writing code against Fillout's API, you don't gain much. But if you want agents to handle "show me my forms" or "revoke this user's token" without custom endpoints, the MCP saves you that plumbing.

Who on the team should connect the Fillout MCP?

Whoever owns your Fillout account and can generate API keys — usually a product or ops lead. If you're using the OAuth tools to let end users authorize their own Fillout accounts, each user will authenticate separately through the consent flow. The initial MCP connection just needs one admin key to enable the tools.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.