Unified Apps Script MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_OAUTH_CLIENT_JSON | No | Path to or contents of the Google OAuth client configuration JSON. Used during authentication setup, but not required if credentials are found elsewhere. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Detect OAuth client and token state; refreshes credentials to verify the connection. |
| auth_setupA | Auto-detect a Desktop OAuth client. If absent, open the Google Auth Platform Clients page; downloaded client JSON is auto-detected from Downloads. |
| auth_loginB | Open the system browser, run Google OAuth with PKCE and a one-shot loopback callback, then store owner-only refresh credentials. |
| auth_logoutA | Revoke stored Google authorization and delete local tokens. Environment-provided tokens cannot be deleted. |
| apps_script_create_projectA | Create a standalone or container-bound Apps Script project. Preserve the returned scriptId. |
| apps_script_get_projectB | Get Apps Script project metadata. |
| apps_script_get_contentB | Read HEAD or an immutable version of all Apps Script project files. |
| apps_script_update_contentA | Update Apps Script HEAD. Merge mode preserves unmentioned files and the manifest; replace mode requires appsscript JSON explicitly. |
| apps_script_create_versionA | Create an immutable version snapshot of HEAD. |
| apps_script_list_versionsC | List immutable versions, automatically following pagination. |
| apps_script_get_versionA | Get one immutable Apps Script version. |
| apps_script_list_deploymentsA | List deployments and entry points, automatically following pagination. |
| apps_script_get_deploymentB | Get one Apps Script deployment. |
| apps_script_create_deploymentC | Deploy an immutable version with a manifest entry point. |
| apps_script_update_deploymentA | Repoint an existing deployment to another immutable version while keeping its deployment ID/URL. |
| apps_script_delete_deploymentA | Permanently delete a deployment and break its live URL. |
| apps_script_run_functionB | Execute a function through an API-executable deployment. The function may cause real external side effects. |
| apps_script_list_processesC | List the authenticated user's Apps Script executions with filters. |
| apps_script_list_script_processesB | List executions for one script with optional API filter syntax. |
| apps_script_get_metricsB | Get execution, user and failure metrics for an Apps Script project. |
| drive_list_apps_script_projectsA | Discover Apps Script project files in Google Drive; unlike Apps Script API, Drive can list projects. |
| apps_script_open_editorB | Open an Apps Script project in the system browser. |
| google_workspace_requestA | Escape hatch for Google Workspace REST APIs not covered by a dedicated tool. Hosts are allowlisted; Authorization headers are injected. Destructive methods require confirm=true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Most tools cleanly map to a distinct resource and action, but apps_script_list_processes and apps_script_list_script_processes could be confused at first glance; their descriptions clarify all-user vs per-script scope. The auth, project, version, and deployment tools are otherwise clearly separated.
The dominant pattern is apps_script_<verb>_<noun>, with auth_* tools following a similar lifecycle convention. drive_list_apps_script_projects and google_workspace_request deviate slightly, but the naming remains predictable and readable overall.
At 23 tools, the set is on the heavy side and spans several sub-domains: auth, Drive discovery, execution, versions, deployments, and metrics. Each tool has a legitimate purpose, but the count is borderline for easy agent navigation.
The toolset mirrors the Apps Script API surface well, covering project creation, content read/write, versioning, deployment lifecycle, execution, processes, and metrics. Auth management, Drive-based project discovery, and a Google Workspace escape hatch fill the remaining workflow gaps.