Google Forms MCP

What Google Forms MCP does

Google Forms MCP exposes Google Forms operations as MCP tools. It can create forms, inspect their questions and settings, update titles and descriptions, change quiz or email-collection settings, add and edit supported question types, reorder items, delete items, and publish or close response collection.

The server also reads submitted responses and individual response records. Responses include timestamps, answers keyed by question ID, respondent email when collection is enabled, and quiz scores when available. A raw request tool provides access to Google Forms API endpoints that do not have dedicated wrappers.

How it works

The server communicates with Google through OAuth 2.0 using the Forms API scopes for form content and read-only responses. Authentication can be completed from the conversation: configure a Desktop-app OAuth client, start login, open the returned authorization URL on the same machine, and finish the login. A local listener on 127.0.0.1 receives the redirect, while tokens are stored in an owner-only local file.

Forms created through the API begin unpublished. Publish them explicitly with create_form or set_publish_settings before sharing the responder URL. Publishing and response collection are separate controls, so a form can remain visible while refusing new submissions.

Form items are addressed by their zero-based positions. Use get_form before modifying, deleting, or moving items, and refresh the form after deletions because later positions shift. Response notifications contain identifiers and event metadata rather than response data; after a notification, retrieve new submissions with list_responses.

Setup and configuration

Node.js 20 or newer and a Google account are required. Add the server to an MCP client with the npm package command:

npx -y mcp-google-forms@latest

Create or select a Google Cloud project, enable the Google Forms API, configure the consent screen, and create a Desktop-app OAuth client. Pass the downloaded client JSON file path to set_client; do not paste its secret into chat. The shared client configuration is stored under ~/.config/mcp-google-auth/client.json, while tokens remain specific to this server.

The package can also use GOOGLE_FORMS_CLIENT_ID, GOOGLE_FORMS_CLIENT_SECRET, and GOOGLE_FORMS_REFRESH_TOKEN in an MCP client configuration. auth_status reports credential source, account, expiry, and OAuth scopes without returning the token. logout revokes locally stored credentials and removes their file, but does not remove environment variables.

Tools and capabilities

• Inspect authentication state and obtain setup instructions.
• Create forms and read complete form definitions, including items, publication state, responder URL, and linked sheet ID.
• Update form information and settings, including quiz mode and email collection modes.
• Add text, paragraph, radio, checkbox, dropdown, scale, date, time, and rating questions.
• Update, delete, and move form items by index.
• Publish or unpublish forms and open or close response collection.
• List responses incrementally with an RFC3339 submitted_after timestamp, paginate results, or fetch one response by ID.
• Create, list, renew, and delete Cloud Pub/Sub watches for response or schema events.
• Send direct Google Forms API requests with raw_request.

Limitations and notes

The Forms API cannot create, edit, or delete submitted responses. File-upload questions cannot be created through the API, and question grids require a raw batch update. The document title, which is the Drive file name, is set during creation and cannot be changed through this server.

Response listing has a lower per-minute quota than other reads, so incremental polling is preferable to repeatedly fetching all responses. Pub/Sub watches expire after seven days, allow one watch per user per form and event type, and are limited to 20 per Cloud project. The notification topic must be in the Google Cloud project and grant publishing permission to Google's Forms notification service account.

Forms created before Google's publication model may not support publication settings. OAuth consent screens left in Testing mode produce refresh tokens that expire after seven days; publishing the consent screen avoids that behavior.