dependency_checkLABSCO 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_checkverifies the environment and confirms the Clasp CLI is set up before anything else runsclasp_setupwalks through the Clasp authentication setupclasp_createprepares a new Apps Script project,clasp_cloneprepares a clone of an existing oneclasp_pullprepares fetching project changes,clasp_push_and_deployprepares the push and deploymentclasp_listreturns 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 — git clone https://github.com/Utakata/google-apps-script-mcp.git
USE CASES
01
Getting Clasp working in the first place
Check the environment and walk through the authentication setup rather than reading the docs twice.
02
Starting a new Apps Script project
Prepare the project creation and continue in your own shell with the command it hands you.
03
Bringing an existing script into local development
Prepare the clone, then pull changes when the script is edited in the browser.
04
Shipping a change
Prepare the push and deployment for the project you are working on.
05
Finding the script you meant
List the projects on the account before guessing at a script ID.
7 tools
Listed in project docs. Your client may show a different list.
clasp_setupclasp_createclasp_cloneclasp_pullclasp_push_and_deployclasp_listBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- Node.js 18 or newer
- GOOGLE_SERVICE_ACCOUNT_KEY or GOOGLE_CREDENTIALS_PATH (one of the two)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/Utakata/google-apps-script-mcp.git
cd google-apps-script-mcp
npm installMCP Clients
Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"google-apps-script-mcp": {
"command": "node",
"args": [
"src/index-security.js"
],
"cwd": "<YOUR_PATH_TO_GOOGLE_APPS_SCRIPT_MCP>",
"env": {
"GOOGLE_SERVICE_ACCOUNT_KEY": "<YOUR_GOOGLE_SERVICE_ACCOUNT_KEY>",
"ENCRYPTION_KEY": "<YOUR_ENCRYPTION_KEY>"
}
}
}
}The block authenticates with a Service Account key in GOOGLE_SERVICE_ACCOUNT_KEY. The project's alternative is OAuth: leave that variable out and set GOOGLE_CREDENTIALS_PATH to your credentials.json instead — one of the two is required.
