Labsco
MCP SERVER

Google Apps Script MCP Server

by Utakata ↗

Walk through Clasp setup and Apps Script project work with an assistant that checks your environment first.

Office Suites & Cloud File Storage
Summary
Read what the stable build actually does before planning around it.

The README is unusually direct about this: the stable build provides preparation and guidance for Clasp operations rather than executing them, with the real commands run in your own shell, and the encrypted property tools live only in the development build. That is worth knowing up front, because the feature list reads much broader than the seven tools you get. `dependency_check` is the right first call — most Clasp problems are environment problems, and it says so before you spend time on the rest.

What it is

An MCP server for Google Apps Script work through the Clasp command-line tool. The stable build carries seven tools that verify your environment and prepare each Clasp operation — creating, cloning, pulling, pushing and listing projects — with the actual Clasp commands run in your own local shell.

What you get
  • `dependency_check` verifies the environment and confirms the Clasp CLI is set up before anything else runs
  • `clasp_setup` walks through the Clasp authentication setup
  • `clasp_create` prepares a new Apps Script project, `clasp_clone` prepares a clone of an existing one
  • `clasp_pull` prepares fetching project changes, `clasp_push_and_deploy` prepares the push and deployment
  • `clasp_list` returns your project list
  • The stable build prepares and guides the Clasp operations; running them stays in your local environment
  • A development build adds encrypted script-property management — set, get, delete and list properties, a security audit, and backup and restore with checksum verification
Requirements

Node.js 18 or newer. The quickest route is the packaged extension file, installed by dragging it into a client that supports extensions, which brings the seven Clasp tools with no dependency setup. Installing manually is `npm install` and launching the server entry point with `node`. Authentication is either a Google Cloud service account key in `GOOGLE_SERVICE_ACCOUNT_KEY` or OAuth credentials through `GOOGLE_CREDENTIALS_PATH` — one of the two is required. `ENCRYPTION_KEY` is recommended and generated automatically if absent, and `LOG_LEVEL` and `MCP_SERVER_NAME` are optional. The Google Apps Script API must be enabled with the script, deployment, metrics and Drive scopes granted.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary