Mcp Google Apps Script
MCP server for the Google Apps Script API: projects, code, versions, deployments and executions.
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.A1-x-Tech/mcp-google-apps-script
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
English | Русский
A1 Google Apps Script MCP lets an AI app write and operate Google Apps Script in plain language. Create a script project, read and edit its code, snapshot versions, manage deployments, run functions and read the execution history.
It uses the Google Apps Script API with your Google account. It distinguishes the editable HEAD code from immutable versions and makes the limits of the Apps Script API explicit instead of implying that every scripting task is possible.
- 13 tools. Create standalone and bound projects, read and update code files, snapshot immutable versions, manage deployments, run functions, and inspect execution history and metrics.
- Versions are immutable. A version snapshots HEAD and can never be edited or deleted; deployments point at versions, so you ship and roll back without changing a URL.
- The manifest always survives. Merge mode keeps the
appsscriptmanifest and every file you did not mention; replace mode refuses a file set without the manifest before any network traffic. - Keep your scriptId. The API cannot list projects and cannot delete them — the
scriptIdreturned bycreate_projectis the only handle. - Minimal Google scopes. Each operation names its own scope (
script.projects,script.deployments,script.processes,script.metrics); request only what your tasks need.
Start with a read-only question:
Show me the files in my report script and which functions failed this week.
Connect the server · Explore use cases · Open technical documentation
See it work in a minute
You: Show the code and the recent runs of my report script.
Assistant: Shows every file with its source and the execution history — which functions ran, when, and which failed. Nothing changes.
You: Add a
formatDatehelper to the Utils file and keep everything else as is.Assistant: Shows the proposed source and confirms that merge mode leaves the other files untouched, then asks for confirmation before writing.
You: Confirm.
Assistant: Writes the file to HEAD. It does not create a version, redeploy or run anything unless you ask separately.
Contents
- Quick start
- What you can ask it to do
- How a project changes
- What can change
- Getting access
- Configuration
- Data, limits and background work
- Technical documentation
- Support
Quick start
You need Node.js 20+, a Google account and OAuth credentials from a Google Cloud project with the Google Apps Script API enabled.
- Prepare Google OAuth access.
- Add the server to your AI app.
- Ask the read-only question above.
Codex
In the app: open Settings → MCP servers, select Add server, choose STDIO, enter the command npx -y mcp-google-apps-script@latest and environment variables GOOGLE_APPS_SCRIPT_CLIENT_ID, GOOGLE_APPS_SCRIPT_CLIENT_SECRET, GOOGLE_APPS_SCRIPT_REFRESH_TOKEN, then select Save and Restart.
From the command line:
From the project's README.