Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Google Apps Script MCP

by A1-x-Techversion 1.1.2i★ –iRuns on your computer
Registry nameio.github.A1-x-Tech/mcp-google-apps-script

Install

Overview

Description from the maker (original English)

MCP server for the Google Apps Script API: projects, code, versions, deployments and executions.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: GOOGLE_APPS_SCRIPT_CLIENT_SECRET, GOOGLE_APPS_SCRIPT_REFRESH_TOKEN, GOOGLE_APPS_SCRIPT_ACCESS_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: GOOGLE_APPS_SCRIPT_CLIENT_ID, GOOGLE_APPS_SCRIPT_CLIENT_SECRET, GOOGLE_APPS_SCRIPT_REFRESH_TOKEN, GOOGLE_APPS_SCRIPT_ACCESS_TOKEN, GOOGLE_APPS_SCRIPT_OAUTH_PORT, GOOGLE_APPS_SCRIPT_API_BASE, GOOGLE_APPS_SCRIPT_TIMEOUT_MS, GOOGLE_APPS_SCRIPT_MAX_RETRIES

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "google-apps-script": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-apps-script"
      ],
      "env": {
        "GOOGLE_APPS_SCRIPT_CLIENT_ID": "your-value",
        "GOOGLE_APPS_SCRIPT_CLIENT_SECRET": "your-value",
        "GOOGLE_APPS_SCRIPT_REFRESH_TOKEN": "your-value",
        "GOOGLE_APPS_SCRIPT_ACCESS_TOKEN": "your-value",
        "GOOGLE_APPS_SCRIPT_OAUTH_PORT": "your-value",
        "GOOGLE_APPS_SCRIPT_API_BASE": "your-value",
        "GOOGLE_APPS_SCRIPT_TIMEOUT_MS": "your-value",
        "GOOGLE_APPS_SCRIPT_MAX_RETRIES": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add google-apps-script --env GOOGLE_APPS_SCRIPT_CLIENT_ID=your-value --env GOOGLE_APPS_SCRIPT_CLIENT_SECRET=your-value --env GOOGLE_APPS_SCRIPT_REFRESH_TOKEN=your-value --env GOOGLE_APPS_SCRIPT_ACCESS_TOKEN=your-value --env GOOGLE_APPS_SCRIPT_OAUTH_PORT=your-value --env GOOGLE_APPS_SCRIPT_API_BASE=your-value --env GOOGLE_APPS_SCRIPT_TIMEOUT_MS=your-value --env GOOGLE_APPS_SCRIPT_MAX_RETRIES=your-value -- npx -y mcp-google-apps-script

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "google-apps-script": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-apps-script"
      ],
      "env": {
        "GOOGLE_APPS_SCRIPT_CLIENT_ID": "your-value",
        "GOOGLE_APPS_SCRIPT_CLIENT_SECRET": "your-value",
        "GOOGLE_APPS_SCRIPT_REFRESH_TOKEN": "your-value",
        "GOOGLE_APPS_SCRIPT_ACCESS_TOKEN": "your-value",
        "GOOGLE_APPS_SCRIPT_OAUTH_PORT": "your-value",
        "GOOGLE_APPS_SCRIPT_API_BASE": "your-value",
        "GOOGLE_APPS_SCRIPT_TIMEOUT_MS": "your-value",
        "GOOGLE_APPS_SCRIPT_MAX_RETRIES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "google-apps-script": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-apps-script"
      ],
      "env": {
        "GOOGLE_APPS_SCRIPT_CLIENT_ID": "your-value",
        "GOOGLE_APPS_SCRIPT_CLIENT_SECRET": "your-value",
        "GOOGLE_APPS_SCRIPT_REFRESH_TOKEN": "your-value",
        "GOOGLE_APPS_SCRIPT_ACCESS_TOKEN": "your-value",
        "GOOGLE_APPS_SCRIPT_OAUTH_PORT": "your-value",
        "GOOGLE_APPS_SCRIPT_API_BASE": "your-value",
        "GOOGLE_APPS_SCRIPT_TIMEOUT_MS": "your-value",
        "GOOGLE_APPS_SCRIPT_MAX_RETRIES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • GOOGLE_APPS_SCRIPT_CLIENT_ID env
    Google OAuth2 client id (refresh-token flow).
  • GOOGLE_APPS_SCRIPT_CLIENT_SECRET secret env
    Google OAuth2 client secret (refresh-token flow). Treat it as a secret.
  • GOOGLE_APPS_SCRIPT_REFRESH_TOKEN secret env
    Google OAuth2 refresh token, exchanged for access tokens automatically. Treat it as a secret.
  • GOOGLE_APPS_SCRIPT_ACCESS_TOKEN secret env
    Static OAuth2 access token (~1h lifetime) — alternative to the refresh-token trio, mostly for testing.
  • GOOGLE_APPS_SCRIPT_OAUTH_PORT env
    Fixed port for the loopback listener of the in-chat login (127.0.0.1 + PKCE). Set it when the client runs over SSH port forwarding; otherwise a free port is picked per login.
  • GOOGLE_APPS_SCRIPT_API_BASE env
    API root override.
  • GOOGLE_APPS_SCRIPT_TIMEOUT_MS env
    Per-request timeout in milliseconds.
  • GOOGLE_APPS_SCRIPT_MAX_RETRIES env
    Retries on transient errors (429 always; 5xx/network for reads).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account A1-x-Tech, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32545 servers in this category
  • Published to the registry more recently than 94% of the other 32545 servers in this category
  • Basic checks equal to or better than 100% of the other 32545 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Google Apps Script MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GOOGLE_APPS_SCRIPT_CLIENT_SECRET, GOOGLE_APPS_SCRIPT_REFRESH_TOKEN, GOOGLE_APPS_SCRIPT_ACCESS_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.2) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Python MCP

by Files-com

Local-only Python MCP server for the Files.com API.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Google Apps Script MCP

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.

  • 19 tools. Create standalone and bound projects, read and update code files, snapshot immutable versions, manage deployments, run functions, and inspect execution history and metrics.
  • Connects from the conversation. Say "connect Google Apps Script": the server walks you through the OAuth client, catches Google's redirect on 127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.
  • 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 appsscript manifest 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 scriptId returned by create_project is 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 formatDate helper 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+ and a Google account. Credentials are not required at install time — the server connects from the conversation.

  1. Add the server to your AI app.
  2. Say "connect Google Apps Script": the assistant walks you through creating the OAuth client and approving access without editing config files.
  3. 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:

codex mcp add google-apps-script \

-- npx -y mcp-google-apps-script@latest

codex mcp list

Codex MCP documentation

Claude Code

claude mcp add \

--transport stdio --scope user google-apps-script \ -- npx -y mcp-google-apps-script@latest

claude mcp list

Claude Code MCP documentation

Claude Desktop

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.

Claude Desktop MCP documentation

Cursor

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"] } } }

Cursor MCP documentation

VS Code

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.

VS Code MCP documentation

What you can ask it to do

Inspect a project and its runs
  • Show this script's files and explain what each function does.
  • Which functions failed this week? Show the execution history for sendDigest.
  • How many users, executions and failures did this script have over the last 7 days?
Write and evolve code
  • Create a standalone project, or a script bound to a Doc, Sheet, Slides or Form.
  • Add a helper function to one file without touching the others.
  • Snapshot the current code as a version with a description before we refactor.
Ship, run and roll back
  • Deploy version 4 and show its entry points — web app URL or API-executable config.
  • Run sendDigest and show the result; if the script throws, show the stack trace.
  • Repoint the deployment back to version 3 without changing its URL.

How a project changes

  1. create_project creates a project — standalone, or bound to a Doc, Sheet, Slides or Form. Keep the returned scriptId: the API cannot list projects.
  2. Code lives at HEAD as files addressed by name without extension. 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.
  3. create_version snapshots HEAD as an immutable version — no edit, no delete, numbers only grow.
  4. A deployment exposes a version as a web app or API executable. Updating a deployment repoints it at another version without changing its URL; the automatic @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.

What can change

OperationWhat happensConfirmation boundary
Read a project, its code, versions, runs or metricsReads dataNo change
Create a projectAdds a standalone or bound script projectChanges Google Apps Script
Update project filesOverwrites code at HEAD; replace mode swaps the entire file setChanges a project
Create a versionAdds an immutable snapshot that can never be removedChanges a project
Create or update a deploymentChanges what a live URL or API endpoint servesChanges a project's live behavior
Delete a deploymentPermanently breaks the deployment URLDestructive
Run a functionExecutes real code with real side effectsDestructive
Raw API requestCan call API methods without a dedicated toolPotentially 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.

Getting access

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.

Connect from the chat (recommended)

Say "connect Google Apps Script" and the assistant runs the flow with you:

  1. 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.
  2. Download that client's JSON ("Download JSON") and give the assistant its path — set_client stores it owner-only. The secret never goes through the conversation.
  3. 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.
  4. 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.

Environment variables (CI, unattended installs)
  1. Create or select a Google Cloud project and enable Google Apps Script API.
  2. Turn on the per-account toggle at script.google.com/home/usersettings — without it every call fails with 403.
  3. Configure the OAuth consent screen and create a Desktop app OAuth client.
  4. 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.
  5. 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 for

Only the beginning is shown; read the rest in the repo

Ask PopNx