MCP Server

MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 19 tools for Google Forms: create quizzes, add questions, set answer keys, read responses.

What you get

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.

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

• Section — Tool
• Auth — auth_status
• Read — get_form
• Add — add_true_false_question
• Edit — update_question_title
• Responses — list_responses

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — Section, Auth, Read and 3 more — is a fair guide to whether it matches your workflow. It is maintained by KamaruSama; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.