Skip to main content
Glama
claude-book

mcp-server-google-forms

by claude-book
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-server-google-forms

No user-submitted related servers found.

    Related Servers

    • google-drive-mcp

      JovemDaniel
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that lets Claude Code interact with Google Sheets, Slides, and Drive, providing tools to read/write spreadsheets, edit presentations, and manage Drive files with OAuth authentication.
      -

    • 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

    • 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
      262 npm
      MIT

    • Ida-Google

      L8teNever
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that integrates with multiple Google services, providing Claude with over 50 tools for managing tasks, contacts, calendar, Gmail, documents, spreadsheets, presentations, chat, and meetings.
      -
    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

    A4.1/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: questions (add/update/delete/move), form metadata (create/get/update info, build), settings (publish, quiz), responses (list), and auth (status). No two tools serve the same purpose, and descriptions clarify any minor overlaps.

    Naming Consistency4/5

    Almost all tools follow a clear verb_noun pattern (e.g., create_form, list_responses, delete_question). The only exception is auth_status, which is a noun phrase, but its purpose is unambiguous and the overall convention is consistent.

    Tool Count5/5

    15 tools is within the well-scoped range for a Google Forms server, covering the full lifecycle (create, read, update, delete questions, manage form settings, list responses). build_form is a convenience wrapper but earns its place.

    Completeness4/5

    The tool set covers core CRUD operations, quiz configuration, and response retrieval. Minor gaps include no direct way to delete a form or list all forms, but these are often handled outside the Forms API and are not critical for typical workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources