Skip to main content
Glama
derek-suwho

Google Forms MCP

by derek-suwho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Google Forms MCP

No user-submitted related servers found.

    Related Servers

    • Google Forms MCP

      naster3
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for reading, editing, and publishing Google Forms with the official Google Forms API. Enables AI agents to programmatically create, modify, and manage forms and responses.
      MIT

    • formslist-mcp

      vaibhavjain2608
      F
      license
      A
      quality
      C
      maintenance
      MCP server for FormsList, a form-backend SaaS. Enables creating form endpoints, reading submissions, configuring auto-responses, and generating embed snippets via natural language.
      7
      -

    • forms-mcp

      yanivmizrachiy
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to persistently manage Google Forms through a remote MCP server, including creating and editing forms, configuring quizzes and scoring, publishing or closing forms, and retrieving responses.
      -

    • mcp-google-forms

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for the Google Forms API that enables creating and editing forms, publishing them, reading responses, and setting up push notifications from AI clients using natural language.
      19
      107 npm
      MIT

    • Argent

      moawhi
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns existing backend APIs (OpenAPI) and SQL databases (PostgreSQL, MariaDB, ClickHouse) into hosted MCP servers for AI clients, with built-in dashboards, forms, and credential encryption.
      2,965 npm
      Apache 2.0
    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

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools map to distinct stages of a draft lifecycle (create/get/patch/undo/publish), so an agent can route most requests cleanly. However, preview_google_form overlaps with update_existing_google_form's preview mode, and publish_form_draft vs update_existing_google_form both write to live Google Forms, creating some boundary ambiguity.

    Naming Consistency4/5

    Names are consistently snake_case with a verb_noun shape (create_form_draft, patch_form_draft, undo_draft_change). Minor deviations exist: the noun is phrased variously as 'form_draft', 'existing_google_form', and the namespace-prefixed google_forms_auth_status breaks the pattern slightly.

    Tool Count5/5

    Eight tools is well-scoped for a draft-based form authoring workflow. Each tool (create, get, patch, undo, preview, publish, update, auth) earns its place without redundancy.

    Completeness4/5

    The draft lifecycle is covered end-to-end: create/get/patch/undo/publish plus preview, update-existing, and auth. Minor gaps remain, such as no delete_form_draft, no way to list drafts, and no read/fetch tool for existing Google Forms beyond updating them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources