Fillout MCP server

What the model can do

Fillout forms: the organisation's forms and their questions, each form's submissions by date, status or words, and one submission; syncs new submissions hourly; can add submissions to a form and delete a submission.

Reads

• fillout_list_formsThe organisation's Fillout forms: name and form id.
• fillout_get_formOne Fillout form's questions (id, text, type), and whether it is a quiz.
• fillout_list_submissionsSubmissions to one Fillout form, newest first by default: when, who from (an email or name answer), quiz score, and the answers, with address, phone…
• fillout_get_submissionOne Fillout submission by form id and submission id, with its answers (address, phone, payment, signature, location and file answers left out).

Acts, when you ask

These change something in Fillout. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• fillout_create_submissionsAdd 1 to 10 submissions to a Fillout form, as if somebody had filled it in.
• fillout_delete_submissionPermanently delete one submission from a Fillout form.

Connect it

First connect Fillout on Dashboard → Connections, then add Memtro to your client once. The Fillout tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Fillout connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How many people filled in the event signup this week?
• › What did Acme put in the contact form?
• › What were the quiz scores on the product training form?
• › Which submissions to the demo request form mention pricing?
• › Delete the test submission I sent to the event signup this morning.

Questions

Is this an official Fillout MCP server?

No. It is Memtro's MCP server with Memtro's Fillout connector behind it: the connector reads Fillout through its API with the credentials you connect on Dashboard → Connections, and Fillout publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Fillout?

Only when you ask, and only what it has been granted: add up to 10 submissions to a Fillout form (may fire the form's own emails and integrations); delete one Fillout submission (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Content and web

• Ahrefs MCP server
• WordPress MCP server
• Webflow MCP server
• Typeform MCP server
• Eventbrite MCP server
• Contentful MCP server