Comprehensive MCP server for the Google Forms API — full coverage of form creation, management, responses, and built-in analytics
Comprehensive MCP server for the Google Forms API — full coverage of form creation, management, responses, and built-in analytics. The google mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.
A comprehensive Model Context Protocol server for the Google Forms API. Enables LLMs to create, manage, and analyze Google Forms.
Everything the assistant can do here goes through one of these:
Category — ToolsForms — create_form, get_form, list_forms, delete_form, update_form_info, update_form_settingsItems — add_question, add_section, add_text_item, update_item, delete_item, move_itemResponses — list_responses, get_responseWatches — create_watch, list_watches, delete_watch, renew_watchComposite — build_form, get_form_summary, get_responses_table, clone_form, export_responses_csvAnalytics — analyze_frequency, cross_tabulate, generate_sankey_data, response_summaryYou will need 3 environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @matthewwolff/google-forms-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google's toolset — Category, Forms, Items and 4 more — is a fair guide to whether it matches your workflow. It is maintained by matthewwolff; 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.
| Tool | What it does |
|---|---|
| Category | Tools |
| Forms | create_form, get_form, list_forms, delete_form, update_form_info, update_form_settings |
| Items | add_question, add_section, add_text_item, update_item, delete_item, move_item |
| Responses | list_responses, get_response |
| Watches | create_watch, list_watches, delete_watch, renew_watch |
| Composite | build_form, get_form_summary, get_responses_table, clone_form, export_responses_csv |
| Analytics | analyze_frequency, cross_tabulate, generate_sankey_data, response_summary |
{
"mcpServers": {
"google-forms-1": {
"command": "npx",
"args": ["-y", "@matthewwolff/google-forms-mcp"],
"env": {
"GOOGLE_CLIENT_ID": "your-value",
"GOOGLE_CLIENT_SECRET": "your-value",
"GOOGLE_REFRESH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_CLIENT_ID | Configuration value read at startup. | Optional |
| GOOGLE_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| GOOGLE_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.