claude-appsscript-pro
Related Servers
Alternatives to claude-appsscript-pro
No user-submitted related servers found.
Related Servers
- 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
- 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.-
- AlicenseAqualityAmaintenanceEnables AI assistants to create and modify Google Apps Script projects, manage versions and deployments, run functions, and inspect execution history through natural language.1333 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to directly read and write Google Apps Script projects, manage versions, deployments, and inspect execution logs to debug triggers.-
- FlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Google Apps Script projects, including project creation, file operations, and web app deployments. It features a security-first design with encrypted property management and automated security auditing for GAS environments.1-
- 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
TDQS
Scored across 74 tools
Numerous tools have overlapping purposes, especially in patching (e.g., apply_code_patch, apply_enhanced_patch, apply_html_patch, plus aliases), deployment, sheet operations, and diagnostics. Aliases further blur distinctions, making it hard for an agent to choose the correct tool.
Names follow a snake_case pattern generally, but there is heavy use of aliases with different names, emojis, and mixed English/Japanese hints. The sheer number and redundancy break any clear naming convention.
74 tools is far too many for an Apps Script server. Many are redundant aliases or overly specialized functions that could be merged or removed. The scope is not justified by the domain.
Despite the large number, the tool set is uneven: heavy on patching and diagnostics but missing basic lifecycle operations like renaming script files. Core CRUD for scripts and sheets is only partly covered, with many edge-case tools bloating the surface.