Skip to main content
Glama

mcp-google-forms

MCP server for managing Google Forms — quizzes, grading, images, responses.

Exposes 19 tools for creating, editing, inspecting, and managing Google Forms through the Model Context Protocol. Built for use with Claude Code, Claude Desktop, or any MCP-compatible client.

📖 อ่านภาษาไทย →


Tools at a glance

Section

Tool

Purpose

Auth

auth_status

Check OAuth credential state

Create / metadata

create_quiz_form

New form in quiz mode

rename_form

Change title/description

set_quiz_mode

Toggle quiz on/off

Read

get_form

Full form JSON

list_questions

Concise item list

verify_answer_keys

Diff current vs expected answer keys

Add

add_true_false_question

Single T/F question

batch_add_true_false

Bulk T/F

add_multiple_choice_question

Radio / checkbox / dropdown

add_text_question

Short or paragraph text

add_section_header

Page break / section

Edit

update_question_title

Rename question

update_true_false_answer

Re-key a T/F answer

delete_question

Remove item

move_question

Reorder

Responses

list_responses

All submitted responses

get_response

One response by ID

Escape hatch

raw_batch_update

Raw Forms API calls


Related MCP server: Google Forms MCP

Install

1. Enable API + get credentials

  1. Go to https://console.cloud.google.com → create/select a project

  2. APIs & Services → Library → enable Google Forms API

  3. OAuth consent screen → External → add yourself as test user

  4. Credentials → Create Credentials → OAuth client ID → Desktop app

  5. Download JSON → save as:

    ~/.config/google-forms-mcp/credentials.json

2. Register with Claude Code

claude mcp add google-forms -s user -- \
  uv run --directory /path/to/mcp-google-forms python server.py

3. First use

On the first tool call, the server opens a browser for OAuth consent. Token is cached at ~/.config/google-forms-mcp/token.json.


Scopes

  • forms.body — create/edit form structure

  • forms.responses.readonly — read responses

  • drive.file — attach images via Drive


Support the project ❤

If this tool helps your workflow, consider supporting development:


Contact


Copyright © 2026 likezara™. All rights reserved. Developed by Kamaru (pen name).

Available Tools

19 tools
add_multiple_choice_questionB

Add a choice question (radio/checkbox/dropdown) with answer key.

Inputs: form_id (required), title (required), options (required), correct_answers (required), +4 more. Returns: object

add_section_headerC

Add a page-break / section header.

Inputs: form_id (required), title (required), description, index. Returns: object

add_text_questionC

Add a short-answer or paragraph text question. Optional answer key.

Inputs: form_id (required), title (required), correct_answers, points, +3 more. Returns: object

add_true_false_questionB

Append (or insert at index) a True/False question with answer key.

Inputs: form_id (required), title (required), correct_answer (required), points, +2 more. Returns: object

auth_statusA

Report whether OAuth credentials and token are in place.

Inputs: no named parameters. Returns: object

batch_add_true_falseA

Bulk add True/False questions.

Each question dict: {"title": str, "correct": bool, "points": int?, "required": bool?}.
If clear_existing=True, deletes all existing items first.

Inputs: form_id (required), questions (required), start_index, clear_existing. Returns: object

create_quiz_formA

Create a new Google Form in quiz mode. Returns formId and responderUri.

Inputs: title (required), document_title. Returns: object

delete_questionC

Delete the item at the given index.

Inputs: form_id (required), index (required). Returns: object

get_formB

Fetch full form metadata, items, and settings.

Inputs: form_id (required). Returns: object

get_responseB

Fetch a single response by id.

Inputs: form_id (required), response_id (required). Returns: object

list_questionsC

Return a concise list of items: index, itemId, title, correctAnswer, points.

Inputs: form_id (required). Returns: result

list_responsesC

List submitted responses for a form.

Inputs: form_id (required). Returns: object

move_questionC

Reorder a question from one index to another.

Inputs: form_id (required), from_index (required), to_index (required). Returns: object

raw_batch_updateC

Escape hatch: pass raw Google Forms API batchUpdate requests.

Inputs: form_id (required), requests (required). Returns: object

rename_formB

Update form's displayed title, description, and/or Drive document title.

Inputs: form_id (required), title, description, document_title. Returns: object

set_quiz_modeC

Toggle quiz grading mode on/off.

Inputs: form_id (required), is_quiz. Returns: object

update_question_titleC

Change the title/text of the question at the given index.

Inputs: form_id (required), index (required), new_title (required). Returns: object

update_true_false_answerB

Update the answer key (correct T/F) for a True/False question at index.

Inputs: form_id (required), index (required), correct_answer (required), points. Returns: object

verify_answer_keysA

Compare current answer keys to an expected list.

Each expected item: {"index": int, "correct": "ถูก"|"ผิด"|str}.
Returns {matches: [...], mismatches: [...]}.

Inputs: form_id (required), expected (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a distinct purpose with clear boundaries. Question type additions are separate, bulk operations are explicitly named, and utility tools like auth_status and raw_batch_update are well-defined.

    Naming Consistency4/5

    Most tools follow verb_noun snake_case pattern. Minor deviations like 'auth_status' (noun instead of verb) and 'raw_batch_update' (adjective prefix) are present but do not significantly hinder consistency.

    Tool Count5/5

    19 tools appropriately cover the scope of Google Forms management including creation, editing, bulk operations, responses, and authentication, without being overwhelming or sparse.

    Completeness4/5

    Core CRUD for questions, form settings, and responses are covered. Missing question types (e.g., linear scale, date) and lack of question type change are minor gaps, but the tool set is sufficient for quiz management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers