mcp-google-apps-script
Related Servers
Alternatives to mcp-google-apps-script
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to directly read and write Google Apps Script projects, manage versions, deployments, and inspect execution logs to debug triggers.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to directly read and write Google Apps Script projects, manage versions and deployments, inspect execution logs and failures, and run functions through natural language, with user-owned OAuth authorization and self-hosted deployment.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to directly read and write Google Apps Script projects, including editing code, managing versions and deployments, and diagnosing trigger failures, with automatic version backups before any write operation.2 npmISC
- AlicenseBqualityDmaintenanceEnables users to create, manage, and execute Google Apps Script projects through natural language. It provides comprehensive tools for code editing, function execution, deployment management, and monitoring script processes.5010MIT
- AlicenseDqualityCmaintenanceEnables AI-driven development and management of Google Apps Script projects, including autonomous system construction, real-time debugging, and spreadsheet operations through natural language.766MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to control Google Workspace services (Slides, Sheets, Drive) through natural language.100 npmISC
TDQS
Scored across 13 tools
Each tool maps to a distinct resource-action pair: projects, content, versions, deployments, metrics, executions, and setup. The few adjacent tools (get_version vs. get_project_content with version_number) are clearly separated by metadata-vs-code descriptions.
Most names follow a clear verb_noun pattern: create_project, get_project_content, list_versions, run_function, list_processes. Minor deviations are raw_request and setup_instructions, which do not use the verb-first convention, but they do not undermine overall readability.
Thirteen tools is well-scoped for the Apps Script lifecycle: project creation, content management, versioning, deployments, execution, and observability. Each tool earns its place, and the escape-hatch raw_request covers edge cases without bloating the surface.
The surface covers the full feasible lifecycle: create/get projects, read/update content, snapshot/list/read versions, manage deployments, run functions, and inspect execution history. Gaps like project deletion or listing are enforced by the upstream API and are mitigated by raw_request and setup_instructions.