apps-script-mcp
Related Servers
Alternatives to apps-script-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to interact with Google Workspace services (Drive, Docs, Sheets, Slides, Forms, Gmail) via OAuth 2.0 authentication and natural language commands.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to manage Google Workspace services such as Calendar, Gmail, and Docs with configurable access and safe-by-design limitations.2-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to read and write Google Sheets, including cell operations, row appending, sheet creation, formatting, and batch updates via the Google Sheets API.MIT
- AlicenseNot gradedqualityDmaintenanceEnables automation of Google Workspace tasks, including reading/writing sheets, generating Apps Script code, and creating webhook senders, with AI assistance via Claude.528 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to read, write, append, create, and clear Google Sheets data using natural language.-
- AlicenseBqualityDmaintenanceProvides integration with the Google Apps Script API, allowing management of script projects, deployments, versions, and executions through any MCP-compatible client like Claude Desktop or VS Code.1660MIT
TDQS
Scored across 8 tools
Most tools map to distinct resources/actions (list/create/get project, write/delete file, bridge_status). The only real overlap is run_code vs run_function, both of which execute code, but the descriptions clearly separate ad-hoc bridge execution from invoking a saved top-level function in a project.
Seven of eight tools follow a clean verb_noun snake_case pattern (run_code, list_projects, create_project, get_project, write_file, delete_file, run_function). bridge_status deviates as a noun-first status query, a minor inconsistency but still readable.
Eight tools is well within the sweet spot and each earns its place: bridge health, raw execution, project lifecycle, file lifecycle, and saved-function invocation. Nothing feels padded or missing at the count level.
The project/file lifecycle is largely covered (list, create, get, write, delete file) plus execution paths. The notable gap is delete_project (and project rename/metadata), though the run_code escape hatch with DriveApp access lets an agent work around it.