A
licenseNot graded
qualityC
maintenanceMCP 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
mcp-google-forms
by A1-x-Tech
Related Servers
Alternatives to mcp-google-forms
No user-submitted related servers found.
Related Servers
- 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.1543 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.7 npm8MIT
TDQS
A4.3/5.0
Scored across 19 tools
Disambiguation4/5
Most tools are clearly distinct (create_form, add_question, update_question, delete_item, move_item, list_responses, get_response). Some potential confusion exists between update_form_info and update_form_settings, and between start_login/finish_login/auth_status, but descriptions clarify the boundaries well.
Naming Consistency4/5
Tool names mostly follow a consistent verb_noun pattern (create_form, get_form, update_form_info, add_question, delete_item, move_item, list_responses). Minor deviations: start_login/finish_login are verb_verb, and set_client/logout/auth_status/setup_instructions don't follow the resource-action pattern, but the overall style is readable and predictable.
Tool Count4/5
19 tools is on the higher end but justified for a Google Forms server covering auth, form CRUD, question management, responses, watches, and a raw API escape hatch. Each tool serves a distinct purpose, though the auth-related tools (6) could arguably be consolidated.
Completeness4/5
The server covers the full form lifecycle: create, read, update info/settings, publish, add/update/delete/move questions, list/get responses, and watch notifications. Minor gaps: no form deletion, no file-upload question support, no response editing (API limitation), and no Drive rename — but these are documented as API limitations or covered by raw_request.
Maintenance
ActivityActive
ResponsivenessNo issues