Skip to main content
Glama
OfirOhan

Fillout MCP Server

by OfirOhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Fillout MCP Server

No user-submitted related servers found.

    Related Servers

    • Filly Forms MCP Server

      eneopt
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes the Filly Forms REST API as MCP tools for AI agents, enabling form type listing, record CRUD, data preview, and document upload with AI extraction.
      MIT

    • niceform-mcp-server

      Shirish-Singh
      A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to create AI-powered forms from natural language descriptions, preview, publish, and close them, and then list, summarize, and export collected responses as CSV. It ships nine tools so an agent can run a form end to end.
      9
      280 npm
      MIT

    • formasty

      QuantumCoderSys
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to build and operate production-ready forms, quizzes, surveys, and workflows, including creation, publishing, submission management, and integration with webhooks and analytics.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    Eight tools is well-scoped for a forms/submissions/webhooks domain, with each tool earning its place. No redundant or filler tools are present.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources