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 gradedqualityNot gradedmaintenanceEnables 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 gradedqualityDmaintenanceEnables 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.9 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
- AlicenseDqualityDmaintenanceEnables AI-driven development and management of Google Apps Script projects, including autonomous system construction, real-time debugging, and spreadsheet operations through natural language.766MIT
- AlicenseAqualityCmaintenanceEnables comprehensive Google Apps Script project lifecycle management (creation, content, versions, deployments, execution, metrics) and controlled access to Google Workspace APIs (Sheets, Docs, Drive, Gmail, Calendar, Tasks, Forms, Slides) with automatic PKCE OAuth and explicit confirmations for destructive actions.23MIT
TDQS
Scored across 18 tools
Tools target clearly distinct resources and actions (auth flow, project CRUD, content, versions, deployments, processes, metrics, run, raw escape hatch), and descriptions disambiguate the tricky pairs (get_version metadata vs get_project_content with version_number, create_version vs manage_deployments action=create). Minor blurring comes from manage_deployments bundling five actions and raw_request overlapping everything, but both are explicitly framed.
The dominant pattern is verb_noun (create_project, get_project_content, list_versions, run_function, finish_login), applied consistently. A few names deviate to noun/state style (auth_status, setup_instructions, raw_request) but remain readable and each fits a distinct role.
18 tools is on the heavier side but justified for a full Apps Script API surface plus the OAuth login flow. Each tool maps to a real operation; only the deployment bundle could arguably be split, so it is slightly over rather than bloated.
Core lifecycle is covered: project create/get, content read/write, versioning, deployments, execution history, metrics, running functions, and a raw_request escape hatch for gaps. Known API limits (no project list/delete) are documented, but the absence of any delete-project or version-delete path means a few dead ends remain.