Google Forms

Google Forms

This connector builds Google Forms and reads their responses through the Google Forms API v1 (https://forms.googleapis.com/v1): it reads a form's questions and settings, creates forms, adds questions of every type, changes title, description, quiz and email settings, publishes or closes a form, reads responses and sets up push notifications. It works with personal Google accounts and Google Workspace, on forms the authorizing Google account owns or can edit.

Setup (one-time, about 10 minutes)

1. Open https://console.cloud.google.com, pick or create a project, then APIs & Services → Library → enable Google Forms API.
2. APIs & Services → OAuth consent screen: choose Internal if you are on Google Workspace (simplest), otherwise External. For External, set the publishing status to In production: while an app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. For your own use, the "unverified app" warning can be clicked through.
3. APIs & Services → Credentials → Create credentials → OAuth client ID → application type Web application → add the authorized redirect URI <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
4. Paste the client ID and secret into GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET and install the connector.
5. On the connector page, click Authorize with Provider and sign in with the Google account whose forms the AI should use. The refresh token is stored encrypted and access tokens are renewed automatically.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector (Gmail, Google Calendar, Google Drive, Google Sheets, Google Docs, Google Slides, Google Forms, Google Contacts, Google Tasks, Search Console, Analytics, Ads). Enable each API in that project, reuse the same GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, and authorize each connector once: each one asks only for its own scopes.

Scopes: the connector asks for https://www.googleapis.com/auth/forms.body (create and edit forms the user can edit) and https://www.googleapis.com/auth/forms.responses.readonly (read their responses). It does not include Google Drive, so it cannot list, search, share or delete form files. For a read-only setup, change the scopes to https://www.googleapis.com/auth/forms.body.readonly https://www.googleapis.com/auth/forms.responses.readonly in the connector's OAuth settings, authorize again, and disable google_forms_create_form, google_forms_add_text_question, google_forms_add_choice_question, google_forms_add_item, google_forms_update_form_info, google_forms_update_settings and google_forms_set_publish_settings.

Switched off at install: google_forms_batch_update (it can change and delete questions) and google_forms_delete_watch. Turn them on per tool if the AI needs them.

Before every change: tell the user what will be created or changed and in which form, and wait for a yes. A published form is live: respondents see edits at once.

Finding a form: the id is in the edit link, https://docs.google.com/forms/d/<id>/edit. The link respondents get (/forms/d/e/<other id>/viewform) carries a different id that the API does not accept. To find a form by name, use the Google Drive connector's gdrive_search_files with mimeType = 'application/vnd.google-apps.form' and name contains '...', or ask the user for the edit link. Forms the user can only fill in cannot be read.

Building a form

1. google_forms_create_form takes only a title: Google refuses questions, description and settings on creation.
2. Add questions in order with google_forms_add_text_question, google_forms_add_choice_question and google_forms_add_item (scale, date, time, rating, grid, section break, text block, image, video). index is the 0-based position: 0 for the first question, then 1, 2... To append to an existing form, pass its current number of items.
3. Set the description with google_forms_update_form_info, and quiz or email collection with google_forms_update_settings.
4. Forms created through the API start unpublished (Google's default since 30 June 2026): publish with google_forms_set_publish_settings (is_published and is_accepting_responses true), then share responderUri from google_forms_get_form. The same tool closes a form to new responses.

• google_forms_batch_update (switched off) changes or removes existing items: updateItem (with an updateMask such as title or questionItem.question.choiceQuestion.options), moveItem, deleteItem. Pass write_control {"requiredRevisionId": "<revisionId>"} to fail instead of editing a form someone changed in between.

Reading responses: google_forms_list_responses returns answers keyed by questionId; read the form once with google_forms_get_form to match each questionId to its question title. Choice answers are the option texts (several for checkboxes), scales the chosen number as text, dates YYYY-MM-DD (MM-DD when the question hides the year, plus HH:MM with a time), file uploads Google Drive file ids. submitted_since filters by submission time. For large forms, page through with page_token, or point the user at the linked Google Sheet (linkedSheetId, readable with the Google Sheets connector).

Notifications (optional): google_forms_create_watch sends a Cloud Pub/Sub message when a response arrives (RESPONSES) or the form changes (SCHEMA). It needs the Cloud Pub/Sub API and a topic in the same Cloud project as the OAuth client, with the role Pub/Sub Publisher granted to [email protected]. A form can have one watch per event type per project; watches expire after 7 days, so renew them with google_forms_renew_watch.

Checking the connection: google_forms_check_authorization shows whether the authorization is valid and which scopes it carries. It does not prove that the Forms API is enabled; the first form call does.

Quotas: Google allows 390 reads and 150 writes per minute per user (975 and 375 per project); listing responses counts as an expensive read, 180 per minute per user. Over the limit it answers 429 RESOURCE_EXHAUSTED: wait a minute and retry. Several edits in one google_forms_batch_update count as one write.

Common errors

• 401: the authorization expired or was revoked (always after 7 days while the consent screen is in Testing). Click Authorize with Provider again.
• 403 PERMISSION_DENIED: the account cannot edit that form, or the scope does not allow the call. 403 "Forms API has not been used in project": enable the Google Forms API in the Cloud project.
• 404: the form id is wrong (often the respondent link's id instead of the edit link's), or the form was deleted.
• 400 on add: index is larger than the number of items, or a choice question has duplicate or empty options. 400 on publishing: an old form without publish settings.

Out of scope here: sharing, copying and deleting forms (Google Drive connector), editing or deleting responses (the API cannot), and Apps Script.