Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COLAB_BINNoPath to the Colab CLI executablecolab
COLAB_MCP_AUTHNoAuthentication mode passed to the Colab CLI: oauth2 or adc (the CLI's --auth)CLI default
COLAB_MCP_DRIVENoEnable the opt-in Google Drive notebooks/projects tools (e.g. 1)
COLAB_MCP_WORKDIRNoThe only local folder the server touchescurrent directory
COLAB_MCP_ENV_FILENoPath to a local NAME=value file with secrets; the model only passes secret names, never values
COLAB_MCP_DRIVE_DIRNoDirectory for the Drive configuration, token and audit log~/.config/colab-mcp/drive
COLAB_MCP_IMAGE_DAYSNoAge after which saved plots are swept (0 = keep)2
COLAB_MCP_MAX_OUTPUTNoMax characters returned per tool call20000
COLAB_MCP_TRASH_DAYSNoAge after which locally trashed notebooks are swept (0 = keep trash)7
COLAB_MCP_DRIVE_AUDITNoPath to the append-only Drive audit log (0600, never stores content)
COLAB_MCP_DRIVE_TOKENNoPath to the Google Drive OAuth token file
COLAB_MCP_MIN_FREE_GBNoFree disk that must remain after a download5
COLAB_MCP_DRIVE_CLIENTNoOAuth client configuration used for Google Drive sign-in
COLAB_MCP_DRIVE_FOLDERNoName of the app folder created in Google DriveColab-MCP
COLAB_MCP_MAX_UPLOAD_MBNoPer-file/zip upload cap (the CLI sends a file in one request)100
COLAB_MCP_DRIVE_PROJECTSNoThe only Drive folder (under MyDrive) the file tools may use when Drive is mounted on the VMColab-MCP
COLAB_MCP_WORKDIR_MAX_GBNoBudget for the working folder (0 = no cap)20
COLAB_MCP_MAX_DOWNLOAD_MBNoCap for unpacked directory downloads1024
COLAB_MCP_DRIVE_COPY_HOURSNoAge after which working copies of Drive notebooks are swept (0 = keep copies)24
COLAB_MCP_DRIVE_MAX_SAVES_PER_HOURNoPer-hour limit on notebook saves60
COLAB_MCP_DRIVE_MAX_LOGINS_PER_HOURNoPer-hour limit on sign-in attempts6
COLAB_MCP_DRIVE_MAX_CREATES_PER_HOURNoPer-hour limit on notebook creations20
COLAB_MCP_DRIVE_MAX_DELETES_PER_HOURNoPer-hour limit on notebook deletions5
COLAB_MCP_DRIVE_MAX_PROJECTS_PER_HOURNoPer-hour limit on project folder creations10

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

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

Tools

Functions exposed to the LLM to take actions

NameDescription
colab_sessionsA

List active Colab runtimes (sessions). Also a quick check that Google sign-in works.

colab_statusB

Show hardware, machine shape and state of a session (or the only active one).

colab_usageA

Show the account's compute-unit balance and current burn rate.

colab_newB

Create a runtime. CPU by default; gpu: T4, L4, G4, H100 or A100; tpu: v5e1 or v6e1; high_mem needs Colab Pro. Consumes compute units until stopped.

colab_ensure_sessionB

Make sure a named session exists: reuse it if colab status finds it, otherwise create it. Safe to call repeatedly.

colab_restart_kernelA

Restart the Jupyter kernel of a session: clears all Python variables but keeps the VM and its files.

colab_urlB

Print the browser URL that attaches the Colab UI to this session (does not open a browser).

colab_runtime_infoB

Report the VM's Python version, CPUs, RAM, free disk and GPU (if any).

colab_stopB

Stop a session and release the VM (stops consuming compute units). Files not downloaded are lost.

colab_installB

Install Python packages on the runtime (uses uv, falls back to pip). Names/specifiers only, e.g. 'qiskit', 'pandas>=2.0'.

colab_execA

Run Python on the runtime; variables persist between calls (same kernel). Give code (text) or file (local .py/.ipynb inside the working directory), not both.

A .ipynb file runs the whole notebook and the CLI writes 'output.ipynb' beside it; for cell-by-cell work use the colab_notebook* tools. secrets: NAMES of variables from the user's secrets file (e.g. ["OPENROUTER_API_KEY"]); they become environment variables in the kernel and their values are never returned. plot_path: local path (inside the working directory) where a displayed image is saved. timeout: seconds (the CLI default is 30).

colab_runA

One-shot job: allocate a fresh VM, run a local script (inside the working directory) with args, then release the VM (or keep it with keep=true).

colab_job_startA

Start a shell command in the background on the VM (e.g. 'python -u train.py --epochs 50') and return a job id. Use for anything longer than a few minutes; poll with colab_job_status / colab_job_logs. Jobs die if the VM is stopped.

colab_job_statusB

State of a background job: running, finished (with exit code), cancelled, or lost.

colab_job_logsC

Last tail lines of a background job's combined stdout/stderr, plus its state.

colab_job_cancelB

Terminate a running background job (SIGTERM to its process group).

colab_job_listC

List all background jobs started on this VM.

colab_notebook_createB

Create a local .ipynb inside the working directory. cells: list of {"type": "code"|"markdown", "source": "..."}.

colab_notebook_listC

List .ipynb files under a directory of the working directory.

colab_notebook_readA

Show a notebook's cells (index, id, type, source) and, optionally, their saved outputs. Use start/end to page through big notebooks.

colab_notebook_add_cellB

Insert a cell. Default is at the end; or give position (index) or after (cell id/index). cell_type: code or markdown.

colab_notebook_edit_cellB

Replace a cell's source (and optionally its type). cell is an id or an index. Clears that cell's stale outputs.

colab_notebook_delete_cellC

Delete one cell by id or index.

colab_notebook_move_cellC

Move a cell to a new index.

colab_notebook_clear_outputsC

Clear saved outputs of one cell, or of all cells.

colab_notebook_run_cellA

Run ONE code cell on the runtime (state persists between cells) and store its output in the notebook. Reports ok/ERROR status. A displayed plot is saved under .colab-mcp/images/.

colab_notebook_run_allA

Run every code cell in order (from index start), storing outputs in the notebook. Stops at the first failing cell unless stop_on_error=false.

colab_notebook_to_scriptA

Convert a notebook to a .py script (markdown becomes comments; lines starting with ! or % are commented out). With out_path, writes the file; otherwise returns the text. Handy before colab_run.

colab_notebook_deleteB

Delete a local notebook by moving it to .colab-mcp-trash/ inside the working directory (recoverable, never a hard delete).

colab_uploadA

Upload one local file (inside the working directory) to the VM, e.g. remote_path '/content/data.csv'. Limited by COLAB_MCP_MAX_UPLOAD_MB (default 100): for big data, download it on the VM instead (colab_exec / colab_job_start).

colab_downloadC

Download one file from the VM into the working directory.

colab_upload_dirA

Upload a whole local folder (inside the working directory) to the VM as one zip, extracted at remote_dir. Skips .git, caches, symlinks and likely secret files (.env, *.key, *.pem...).

colab_download_dirA

Download a whole VM folder into local_dir (inside the working directory) via one zip. Refuses archives whose paths escape the target or exceed COLAB_MCP_MAX_DOWNLOAD_MB (default 1024).

colab_lsC

List files in a VM directory (default /content).

colab_rmB

Delete ONE file on the VM (not on the user's computer). Refuses root-like paths.

colab_drive_statusA

Is Google Drive mounted on this session? Reports yes/no and free space only (never lists your files). If it is not mounted, use colab_drive_mount_start (the user approves in the browser).

colab_drive_mount_startA

Step 1 of mounting Google Drive on a session: opens Google's approval page in the user's browser. The link itself is NOT returned (it contains the account e-mail) unless the browser could not be opened or show_link=true. The USER must click Allow; never ask for or handle passwords or codes. WARNING: once mounted, code running on the VM can reach the user's WHOLE Drive; mount only when asked, and stop the session afterwards. Then call colab_drive_mount_finish.

colab_drive_mount_finishA

Step 2 of mounting Google Drive: call it AFTER the user says they clicked Allow. Completes the mount; then verify with colab_drive_status. cancel=true abandons a pending mount.

colab_drive_project_dirA

Create (if missing) and return a project folder on the mounted Drive: /content/drive/MyDrive//. Use it for big datasets, checkpoints and results that must survive the session. Requires Drive to be mounted (see colab_drive_status).

colab_logA

Last lines entries of a session's history (event_type e.g. execution, file_operation). Without a session, lists sessions that have logs.

colab_local_footprintA

Show how much this tool keeps on your computer (temp files, plots, local trash), free disk and the working-directory budget. Read-only.

colab_local_cleanupA

Delete everything this tool keeps only temporarily on your computer: transfer zips, saved plots and old local trash. Never touches your notebooks, data or anything outside those folders.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 42 tools

Disambiguation4/5

Most tools target a distinct resource+action, and descriptions carefully distinguish near-pairs (colab_exec vs colab_run vs colab_job_start; colab_upload vs colab_upload_dir). Some boundary blur remains between session-inspection tools (colab_sessions, colab_status, colab_runtime_info) and between colab_new and colab_ensure_session, but guidance is generally clear.

Naming Consistency4/5

All tools share the colab_ prefix and snake_case, with clear resource-grouping (colab_notebook_*, colab_job_*, colab_drive_*). Minor deviation: a mix of noun-style (colab_sessions, colab_status) and verb-style (colab_new, colab_stop) names, and colab_new is less descriptive than its siblings.

Tool Count2/5

42 tools is well above the comfortable range for a single server. Although the domain is broad (sessions, exec, jobs, notebooks, files, Drive), the granular cell-level notebook surface (create, add/edit/delete/move/clear/run_cell/run_all/read/list/to_script) plus parallel file vs directory transfer tools inflate the count considerably.

Completeness4/5

Coverage is broad and lifecycle-complete: session create/ensure/status/stop, exec and one-shot runs, background jobs with status/logs/cancel/list, full notebook and cell CRUD, upload/download for files and directories, and Drive mount/status/project-dir. Minor gaps like no kernel interrupt (only restart) and no directory-delete operation are easy to work around.

Maintenance

ActivityMaintained
ResponsivenessNo issues