# Google Forms MCP (npm · mcp-google-forms)

MCP server for the Google Forms API: create forms, manage questions, read responses and watches.

- Trust score: 67/100 (medium)
- Change this week: +29
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- npm · `mcp-google-forms`: 67/100 (this document), [markdown](https://verifymcp.io/servers/a1-x-tech-mcp-google-forms/mcp-google-forms.md), [page](https://verifymcp.io/servers/a1-x-tech-mcp-google-forms/mcp-google-forms)

## Channel facts

- Registry: `npm`
- Package: `mcp-google-forms`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2927 tokens (~225/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add a1-x-tech-mcp-google-forms -- npx -y mcp-google-forms
```

### Codex

```bash
codex mcp add a1-x-tech-mcp-google-forms -- npx -y mcp-google-forms
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "a1-x-tech-mcp-google-forms": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-google-forms"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add a1-x-tech-mcp-google-forms --command npx --arg -y --arg mcp-google-forms
```

### Hermes

```yaml
mcp_servers:
  a1-x-tech-mcp-google-forms:
    command: "npx"
    args: ["-y", "mcp-google-forms"]
```

### Other

```json
{
  "mcpServers": {
    "a1-x-tech-mcp-google-forms": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-forms"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-19 (score 67, +15)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 1.0.0 → 1.1.0

### 2026-08-18 (score 52, +14)

- [security regression] Malware scan: pass → unverified
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] Package version: 1.0.0 → 1.1.0

### 2026-08-11 (score 38, 0)

- [functional] Package version: 0.1.0 → 1.0.0
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 38)

First indexed and scored.

## MCP tools (13)

### `create_form` (~205 tokens)

Create a form

Creates a new Google Form and returns it (formId, revisionId, responderUri, publishSettings). The API only accepts a title and an optional document title at creation (the Drive file name — it cannot be changed later through this API) — add questions with add_question and change settings with update_form_settings afterwards. IMPORTANT: API-created forms are UNPUBLISHED by default and do not accept responses; pass publish=true to publish immediately, or call set_publish_settings later. If the chained publish step fails, the form still exists: the result carries formId with published:false and publish_error — finish with set_publish_settings, never create_form again. Share the responderUri with respondents once published.

Input parameters:

- `document_title` (string): The document name in Google Drive (defaults to the title).
- `publish` (boolean): Publish the form right away so it accepts responses (default false — the form stays an unpublished draft).
- `title` (string, required): The form title shown to respondents.

### `get_form` (~118 tokens)

Get a form

Returns the full form: info (title, description), settings (quiz mode, email collection), items[] with their itemId/questionId and question definitions, publishSettings, responderUri and linkedSheetId. Items are returned in order — their 0-based positions are the indexes that update_question, delete_item and move_item address, so call this before mutating items.

Input parameters:

- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.

### `update_form_info` (~153 tokens)

Update form info

Changes the form's title and/or description. Only the provided fields are touched (the updateMask is computed automatically); at least one field is required. The document title (the Drive file name) is set once at create_form and cannot be changed through the Forms API — renaming the file needs the Drive API, which this server does not cover. Returns the batchUpdate replies with the new revisionId.

Input parameters:

- `description` (string): New form description shown under the title.
- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `title` (string): New form title shown to respondents.

### `update_form_settings` (~177 tokens)

Update form settings

Toggles quiz mode (grading with points) and/or the email collection mode. Quiz mode only enables grading — points, correct answers and feedback are set per question afterwards via update_question with the questionItem.question.grading mask (add_question cannot set them). email_collection_type: DO_NOT_COLLECT, VERIFIED (respondent must be signed in; email verified) or RESPONDER_INPUT (respondent types an email). At least one field is required; only the provided fields are touched.

Input parameters:

- `email_collection_type` (string): How respondent emails are collected.
- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `is_quiz` (boolean): Turn quiz mode on/off (enables per-question grading).

### `set_publish_settings` (~174 tokens)

Publish or unpublish a form

Publishes or unpublishes the form and opens/closes response collection. is_accepting_responses defaults to mirroring is_published (publish = start accepting, unpublish = stop). Use is_published=true with is_accepting_responses=false to keep a published form visible but closed. Fails on legacy forms created before the publish model existed — those are managed only in the Forms UI.

Input parameters:

- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `is_accepting_responses` (boolean): Whether the form accepts new responses (defaults to the value of is_published).
- `is_published` (boolean, required): true = published (respondents can open it), false = unpublished draft.

### `add_question` (~460 tokens)

Add a question

Adds a question to the form (a convenience wrapper over batchUpdate createItem). Types: text (short answer), paragraph (long answer), radio (single choice), checkbox (multiple choice), dropdown, scale (linear scale low..high), date, time, rating (stars/hearts/thumbs). Choice types require options[]. Returns the created itemId and questionId from the batchUpdate replies. index inserts at that 0-based position; omit it to append at the end (costs one extra read to count items). Quiz grading (points, correct answers, feedback) cannot be set here — after adding, use update_question with the questionItem.question.grading mask. File-upload questions cannot be created via the API, and question grids (questionGroupItem) need raw_request with a batchUpdate body.

Input parameters:

- `description` (string): Help text shown under the question.
- `duration` (boolean): Time question asks for an elapsed duration instead of a time of day.
- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `high` (integer): Scale upper bound (default 5; scale type).
- `high_label` (string): Label for the highest scale point.
- `include_time` (boolean): Date question also asks for a time of day.
- `include_year` (boolean): Date question includes the year.
- `index` (integer): 0-based position to insert at; omitted = append after the last item.
- `low` (integer): Scale lower bound (default 1; scale type).
- `low_label` (string): Label for the lowest scale point.
- `options` (array): The choices — required for radio, checkbox and dropdown.
- `rating_icon_type` (string): Rating icon (default star).
- `rating_scale_level` (integer): Number of rating icons (3..10; default 5; rating type).
- `required` (boolean): Whether an answer is required to submit.
- `shuffle` (boolean): Shuffle option order per respondent (choice types).
- `title` (string, required): The question text shown to respondents.
- `type` (string, required): The question type.

### `update_question` (~217 tokens)

Update an item

Updates an existing item (question or other) via batchUpdate updateItem. The item is addressed by its 0-based index — call get_form first to see current positions and the item's current shape. item is a raw Forms API Item object with the new values; update_mask names the fields to replace, e.g. "title" or "title,questionItem.question.required". Only masked fields change; masking a field the item object leaves unset clears it.

Input parameters:

- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `index` (integer, required): 0-based position of the item to update (from get_form).
- `item` (object, required): The Forms API Item object with the new values, e.g. {"title":"New title","questionItem":{"question":{"required":true}}}.
- `update_mask` (string, required): Comma-separated field paths to replace, e.g. "title,questionItem.question.required".

### `delete_item` (~105 tokens)

Delete an item

Deletes the item at the given 0-based index (question, page break, text block, ...). Deletion shifts every later item one position down — re-check indexes with get_form between successive deletes.

Input parameters:

- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `index` (integer, required): 0-based position of the item to delete (from get_form).

### `move_item` (~106 tokens)

Move an item

Moves the item at from_index to to_index (both 0-based, to_index is the position after removal). Use get_form to see the current order first.

Input parameters:

- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `from_index` (integer, required): Current 0-based position of the item.
- `to_index` (integer, required): Target 0-based position.

### `list_responses` (~258 tokens)

List form responses

Lists submitted responses: responseId, createTime, lastSubmittedTime, respondentEmail (only when email collection is on), answers keyed by questionId (map questionId → question via get_form), and totalScore for graded quizzes. submitted_after keeps only responses submitted strictly after that RFC3339 UTC timestamp — the API's only filter; there is no ordering or email filter, do that client-side. Paginate with page_token from nextPageToken. Note: this endpoint has a lower per-minute quota than other reads — poll incrementally with submitted_after rather than re-listing everything. The API is read-only for responses; submitting them programmatically is impossible.

Input parameters:

- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `page_size` (integer): Max responses per page (1..5000; the API's default and max is 5000).
- `page_token` (string): nextPageToken from the previous page.
- `submitted_after` (string): Only responses submitted after this RFC3339 UTC timestamp, e.g. 2026-08-01T00:00:00Z (exclusive).

### `get_response` (~106 tokens)

Get one response

Fetches a single submission by its responseId (from list_responses): answers keyed by questionId, createTime, lastSubmittedTime, respondentEmail and totalScore when available. Map questionId to the question text via get_form.

Input parameters:

- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `response_id` (string, required): The response id from list_responses.

### `manage_watches` (~291 tokens)

Manage push-notification watches

Manages Cloud Pub/Sub push-notification watches on a form. action=create needs event_type (RESPONSES = new submissions, SCHEMA = form structure changes) and topic_name; the topic must live in your Cloud project and grant the Pub/Sub Publisher role to forms-notifications@system.gserviceaccount.com. action=list shows your watches; delete and renew need watch_id. Watches expire after 7 days — renew extends 7 days from now and reactivates a SUSPENDED watch. Notifications carry only formId/watchId/eventType attributes (no payload): on RESPONSES call list_responses with submitted_after, on SCHEMA call get_form. Limits: 1 watch per user per form+event type, 20 per Cloud project.

Input parameters:

- `action` (string, required): What to do with the form's watches.
- `event_type` (string): create only: RESPONSES (new submissions) or SCHEMA (form structure/settings changes).
- `form_id` (string, required): The form id — the long id from the form URL (docs.google.com/forms/d/<formId>/edit) or from create_form output.
- `topic_name` (string): create only: the Cloud Pub/Sub topic, e.g. projects/my-project/topics/forms-events.
- `watch_id` (string): delete/renew: the watch to target. create: optional custom id (auto-generated if omitted).

### `raw_request` (~201 tokens)

Raw Google Forms API call

Escape hatch to call any Google Forms API v1 path directly, for requests the typed tools don't cover — e.g. a batchUpdate with questionGroupItem grids, writeControl/requiredRevisionId, includeFormInResponse, or several requests at once: path "v1/forms/<formId>:batchUpdate", method POST, body {"requests":[...]}. The path may carry a query string (e.g. "v1/forms/<id>/responses?filter=timestamp%20%3E%202026-08-01T00:00:00Z"). The Bearer token is added automatically; the method defaults to GET.

Input parameters:

- `body` (object): JSON request body (POST only).
- `method` (string): HTTP method (the Forms API uses only these three). Defaults to GET.
- `path` (string, required): API path relative to https://forms.googleapis.com, e.g. "v1/forms/<formId>:batchUpdate".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/a1-x-tech-mcp-google-forms/mcp-google-forms#diagnostics

## Score history

- 2026-08-20: 67
- 2026-08-19: 67
- 2026-08-18: 52
- 2026-08-17: 38
- 2026-08-16: 38
- 2026-08-15: 38
- 2026-08-14: 38
- 2026-08-13: 38
- 2026-08-12: 38
- 2026-08-11: 38
- 2026-08-10: 38
- 2026-08-09: 38

## Links

- npm package: https://www.npmjs.com/package/mcp-google-forms
- Socket report: https://socket.dev/npm/package/mcp-google-forms
- Repository: https://github.com/A1-x-Tech/mcp-google-forms
- Changelog RSS feed: https://verifymcp.io/servers/a1-x-tech-mcp-google-forms/mcp-google-forms.xml
- Changelog JSON feed: https://verifymcp.io/servers/a1-x-tech-mcp-google-forms/mcp-google-forms.json
- HTML version of this page: https://verifymcp.io/servers/a1-x-tech-mcp-google-forms/mcp-google-forms