mcp-google-forms
Related Servers
Alternatives to mcp-google-forms
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for reading, editing, and publishing Google Forms with the official Google Forms API. Enables AI agents to programmatically create, modify, and manage forms and responses.MIT
- FlicenseAqualityCmaintenanceMCP server for FormsList, a form-backend SaaS. Enables creating form endpoints, reading submissions, configuring auto-responses, and generating embed snippets via natural language.7-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with Google Docs, Sheets, and Drive using the user's own Google account.-
- AlicenseAqualityAmaintenanceAn MCP server that lets Claude Code create, edit, and publish Google Forms, including quizzes and response management, using OAuth with a verified Google app. It provides 15 tools for form building, publishing, and analyzing responses.1536 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Google Sheets through natural language, allowing users to create, read, update, and manage spreadsheet data via the Google Sheets API v4.-
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server integrating Google Docs, Sheets, Drive, Gmail, Calendar, and Apps Script APIs, featuring unique Apps Script support for AI-driven automation.3 npm8MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: form-level reads/writes, item mutations, response reads, watch management, and a raw escape hatch. Tools like update_form_info, update_form_settings, and set_publish_settings have clearly separated concerns, so there is little risk of misselection.
Most names follow a clear verb_noun snake_case pattern: get_form, update_question, list_responses, move_item. Minor inconsistencies exist, such as add_question vs create_form, set_publish_settings vs update_*, and raw_request not following the verb_noun convention.
With 13 tools, the server is well-scoped for managing Google Forms: CRUD for forms and items, response access, watch management, and an escape hatch. Each tool earns its place without redundancy or excessive surface area.
The tool set covers the core form lifecycle, item mutations, response reading, publish settings, and watches. Minor gaps exist, such as no typed way to add page breaks/text items or set grading during question creation, but the raw_request escape hatch and documented update_question workflow provide workarounds.