Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APPS_SCRIPT_BRIDGE_KEYYesThe secret key copied from the execution log when running the bridge's setup function.
APPS_SCRIPT_BRIDGE_URLYesThe /exec URL of the deployed Apps Script web app bridge.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Edit and run Google Apps Script as the signed-in Google user through a personal web app bridge. Use run_code for one-off snippets (Sheets, Docs, Drive, Gmail, Calendar), and the project tools to read, write and run standalone script projects. Call bridge_status first if anything fails.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
bridge_statusA

Check the bridge: its version, the Google account it runs as, and whether the Drive service is enabled (needed to create and edit projects).

run_codeA

Run Apps Script (JavaScript, V8) as the user and return the result and logs.

code is a function body: use return to send back a JSON-serializable value. All built-in services are available (SpreadsheetApp, DocumentApp, DriveApp, GmailApp, CalendarApp, UrlFetchApp, ...). console.log and Logger.log output is returned in logs. There is no active document, so open files by ID or URL. Executions stop after 6 minutes.

list_projectsA

List standalone Apps Script projects in the user's Drive, optionally filtered by a title substring. Scripts bound to a Sheet/Doc/Form are not listed, but work with the other tools when you pass their script ID.

create_projectB

Create a standalone Apps Script project with an empty Code file.

get_projectA

Get a standalone project's title and every file with its full source. script_id is the ID in the editor URL (script.google.com/d//edit).

write_fileA

Create or fully replace one file in a project; other files are kept.

name has no extension ("Code", not "Code.gs"). type defaults to SERVER_JS, or JSON for the "appsscript" manifest; use HTML for HtmlService templates.

delete_fileB

Delete one file from a project (the appsscript manifest cannot be deleted).

run_functionA

Run a top-level function from a project's saved code and return its result and logs.

The project's .gs files are loaded into the bridge and executed there, so it runs as the user but outside the real project: there is no active document (getActiveSpreadsheet() returns null), and the project's own libraries, advanced services, script properties and triggers are not available. Only standalone projects can be loaded. args must be JSON-serializable.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation4/5

Most tools map to distinct resources/actions (list/create/get project, write/delete file, bridge_status). The only real overlap is run_code vs run_function, both of which execute code, but the descriptions clearly separate ad-hoc bridge execution from invoking a saved top-level function in a project.

Naming Consistency4/5

Seven of eight tools follow a clean verb_noun snake_case pattern (run_code, list_projects, create_project, get_project, write_file, delete_file, run_function). bridge_status deviates as a noun-first status query, a minor inconsistency but still readable.

Tool Count5/5

Eight tools is well within the sweet spot and each earns its place: bridge health, raw execution, project lifecycle, file lifecycle, and saved-function invocation. Nothing feels padded or missing at the count level.

Completeness4/5

The project/file lifecycle is largely covered (list, create, get, write, delete file) plus execution paths. The notable gap is delete_project (and project rename/metadata), though the run_code escape hatch with DriveApp access lets an agent work around it.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues