Listed from the MCP registry; nobody on Odel publishes it.
MCP server for the Google Apps Script API: projects, code, versions, deployments and executions.
Runs on your machine from its package; the steps are below.

At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y mcp-google-apps-script
MCP client config
{
"mcpServers": {
"google-apps-script-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-google-apps-script"
]
}
}
}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.
127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.appsscript manifest and every file you did not mention; replace mode refuses a file set without the manifest before any network traffic.scriptId returned by create_project is the only handle.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
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.
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
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:
codex mcp add google-apps-script \
-- npx -y mcp-google-apps-script@latest
codex mcp list
claude mcp add \
--transport stdio --scope user google-apps-script \
-- npx -y mcp-google-apps-script@latest
claude mcp list
The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
{
"mcpServers": {
"google-apps-script": {
"command": "npx",
"args": ["-y", "mcp-google-apps-script@latest"]
}
}
}
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-apps-script": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-apps-script@latest"]
}
}
}
Run MCP: Open User Configuration and add:
{
"servers": {
"google-apps-script": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-apps-script@latest"]
}
}
}
Check it with MCP: List Servers.
sendDigest.sendDigest and show the result; if the script throws, show the stack trace.create_project creates a project — standalone, or bound to a Doc, Sheet, Slides or Form. Keep the returned scriptId: the API cannot list projects.update_project_content merges by default — it upserts the files you name and keeps the rest — and only replaces the entire set when asked; the appsscript manifest can never be deleted.create_version snapshots HEAD as an immutable version — no edit, no delete, numbers only grow.@HEAD deployment cannot be deleted.The API cannot delete a project either — that means deleting its Drive file, which this server does not cover. run_function requires an API-executable deployment, an OAuth client from the same Cloud project as the script and the script's own scopes on the token; Apps Script stops any execution after 6 minutes. The execution history shows status and timing but no error messages — those live in Cloud Logging or come from re-running the function.
| Operation | What happens | Confirmation boundary |
|---|---|---|
| Read a project, its code, versions, runs or metrics | Reads data | No change |
| Create a project | Adds a standalone or bound script project | Changes Google Apps Script |
| Update project files | Overwrites code at HEAD; replace mode swaps the entire file set | Changes a project |
| Create a version | Adds an immutable snapshot that can never be removed | Changes a project |
| Create or update a deployment | Changes what a live URL or API endpoint serves | Changes a project's live behavior |
| Delete a deployment | Permanently breaks the deployment URL | Destructive |
| Run a function | Executes real code with real side effects | Destructive |
| Raw API request | Can call API methods without a dedicated tool | Potentially destructive |
The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish an inspection from a live change.
Google Apps Script requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.
Say "connect Google Apps Script" and the assistant runs the flow with you:
setup_instructions prints the checklist: create or select a Google Cloud project, enable Apps Script API, configure the consent screen and create a Desktop app OAuth client.set_client stores it owner-only. The secret never goes through the conversation.start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.finish_login exchanges the code and saves the tokens to ~/.config/mcp-google-apps-script/credentials.json (mode 0600) and verifies them with a real Apps Script API call — so an API that is still switched off is caught right there.The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it.
Create or select a Google Cloud project and enable Google Apps Script API.
Turn on the per-account toggle at script.google.com/home/usersettings — without it every call fails with 403.
Configure the OAuth consent screen and create a Desktop app OAuth client.
Authorize the Google account that owns the scripts. The OAuth 2.0 Playground can obtain the refresh token when Use your own OAuth credentials is enabled.
Request the scopes for the tools you plan to use:
https://www.googleapis.com/auth/script.projects
https://www.googleapis.com/auth/script.deployments
https://www.googleapis.com/auth/script.processes
https://www.googleapis.com/auth/script.metrics
For inspection-only use, replace the first two with the read-only variants script.projects.readonly and script.deployments.readonly; list_processes and get_project_metrics still need script.processes and script.metrics, which have no narrower form. run_function needs none of these scopes — instead the token must carry every scope the target script itself uses, and the OAuth client must belong to the same Cloud project as the script.
Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.
The setup_instructions tool returns this same checklist and works even before credentials are configured.
Every variable is optional — with none of them the server connects from the chat.
| Variable | Required | Description |
|---|---|---|
GOOGLE_APPS_SCRIPT_CLIENT_ID | No* | OAuth client ID. |
GOOGLE_APPS_SCRIPT_CLIENT_SECRET | No* | OAuth client secret. |
GOOGLE_APPS_SCRIPT_REFRESH_TOKEN | No* | OAuth refresh token. |
GOOGLE_APPS_SCRIPT_ACCESS_TOKEN | No* | Short-lived alternative to the OAuth trio. |
GOOGLE_APPS_SCRIPT_OAUTH_PORT | No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
GOOGLE_APPS_SCRIPT_API_BASE | No | Google Apps Script API base URL override. |
GOOGLE_APPS_SCRIPT_TIMEOUT_MS | No | Per-request timeout; default 60000 ms. |
GOOGLE_APPS_SCRIPT_MAX_RETRIES | No | Temporary-error retries; default 3. |
* Provide either the OAuth trio or an access token.
#; a value from your request can appear in it if the error text contains it. Set ASKADS_TELEMETRY=0 to opt out.429, the server uses backoff; reads also retry after network and 5xx errors, while writes are not replayed after an uncertain failure — a duplicated create_version piles up immutable versions, and a duplicated run_function executes side effects twice. After an ambiguous failure, check list_versions or the execution history instead of re-sending.Found a bug or need a scenario? Create an issue or write in Telegram.
You made it to the end!