mcpdirectory.dev
9,129 servers · updated 23 Sept

Google Apps Script MCP server

official from A1 X Tech Active last commit 2 d
{
  "mcpServers": {
    "a1-x-tech-google-apps-script": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-apps-script@latest"
      ],
      "env": {
        "GOOGLE_APPS_SCRIPT_CLIENT_ID": "<google_apps_script_client_id>",
        "GOOGLE_APPS_SCRIPT_CLIENT_SECRET": "<google_apps_script_client_secret>",
        "GOOGLE_APPS_SCRIPT_REFRESH_TOKEN": "<google_apps_script_refresh_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y mcp-google-apps-scriptversion 0.1.0

What it does

An MCP server that lets you create, read, edit and deploy Google Apps Script projects using the Google Apps Script API. Designed for developers who want to manage script code, versions, deployments and execution history through an AI assistant.

  • Create a new standalone or bound Google Apps Script project and write initial code
  • Read the source code of existing script files and view recent function execution history to debug failures
  • Update code in HEAD, create immutable version snapshots, and manage deployments without affecting other files

Tools this server exposes

ToolDoes
create_projectCreate a new standalone or bound Google Apps Script project
read_projectGet project metadata and list all files in the project
read_codeRead the source code of a specific file
write_codeUpdate code in HEAD with merge or replace mode
create_versionSnapshot the current HEAD code as an immutable version
read_versionsList all versions of a project
create_deploymentCreate a deployment pointing to a specific version
read_deploymentsList all deployments of a project
remove_deploymentDelete a deployment
run_functionExecute a function in the script project
read_execution_historyView the execution history and results of script functions
read_metricsGet execution metrics and performance data
list_projectsList Google Apps Script projects

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.