Server data from the Official MCP Registry
Synchronize Colab notebook files through Google Drive without executing notebook code.
Synchronize Colab notebook files through Google Drive without executing notebook code.
Valid MCP server (1 strong, 4 medium validity signals). 3 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry.
8 files analyzed · 4 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: COLAB_MCP_ROOT
Environment variable: COLAB_MCP_DRIVE_ACCESS
Environment variable: COLAB_MCP_GOOGLE_CREDENTIALS
Environment variable: COLAB_MCP_GOOGLE_TOKEN
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-yummytastycode-colab-drive-mcp": {
"env": {
"COLAB_MCP_ROOT": "your-colab-mcp-root-here",
"COLAB_MCP_DRIVE_ACCESS": "your-colab-mcp-drive-access-here",
"COLAB_MCP_GOOGLE_TOKEN": "your-colab-mcp-google-token-here",
"COLAB_MCP_GOOGLE_CREDENTIALS": "your-colab-mcp-google-credentials-here"
},
"args": [
"colab-drive-mcp"
],
"command": "uvx"
}
}
}From the project's GitHub README.
An MCP server for safely inspecting, editing, and synchronizing
Google Colab-compatible .ipynb notebooks through Google Drive.
[!IMPORTANT] This is a notebook file synchronization server, not a notebook execution service. It transfers and edits
.ipynbfiles through Google Drive. It does not connect to Colab runtimes, execute cells, click Run all, keep sessions alive, automate the Colab browser UI, or bypass Colab limits.
Use this MCP when an AI agent needs to prepare a notebook locally, synchronize it with Drive, inspect completed outputs, or return an edited notebook to the user. Open and execute the synchronized notebook separately in Colab, Jupyter, VS Code, or another notebook runtime.
Run all, or unattended Colab sessions.The MCP initialization response includes server-wide instructions that define this project as file synchronization only. Tool descriptions repeat the same boundary where it matters.
manifest.0 provides the same purpose, capabilities, and
non-goals as a typed Zero language contract for agents and repository tooling.
get_google_drive_status: diagnose dependencies, credentials, token, and scope.authorize_google_drive: explicitly open the Google OAuth browser flow.list_local_notebooks, get_local_notebook, create_local_notebookadd_local_cell, update_local_cell, delete_local_cellsearch_local_cells, clear_local_outputslist_drive_notebooks, pull_drive_notebook, push_local_notebookcopy_drive_notebook, get_colab_urlpull_drive_notebook and push_local_notebook synchronize notebook files.
They never execute notebook code. get_colab_url returns a URL but does not
open a browser.
Run directly from PyPI with uvx:
COLAB_MCP_ROOT="$HOME/notebooks" uvx --from 'colab-drive-mcp[drive]' colab-drive-mcp
Or install from source:
git clone https://github.com/YummyTastyCode/colab-drive-mcp.git
cd colab-drive-mcp
python3 -m venv .venv
.venv/bin/pip install -e '.[drive]'
Run the server:
COLAB_MCP_ROOT="$HOME/notebooks" .venv/bin/colab-drive-mcp
Local tools can access only .ipynb files below COLAB_MCP_ROOT.
The server is published in the official MCP Registry as:
io.github.YummyTastyCode/colab-drive-mcp
First call get_google_drive_status. It does not open a browser or modify
files. Its response explains the next required step.
To enable Drive:
~/.config/colab-mcp/credentials.json.authorize_google_drive and complete the Google sign-in flow.The resulting token is stored at ~/.config/colab-mcp/token.json.
Override these locations with:
COLAB_MCP_GOOGLE_CREDENTIALSCOLAB_MCP_GOOGLE_TOKENNever commit OAuth credentials or tokens.
The default mode is file, using Google's narrower drive.file scope:
COLAB_MCP_DRIVE_ACCESS=file
This mode can access files created or explicitly opened by this OAuth app. It cannot reliably list all existing notebooks in a user's Drive.
To find and update existing Drive notebooks, explicitly enable full access:
COLAB_MCP_DRIVE_ACCESS=full
Changing access modes may require deleting token.json and calling
authorize_google_drive again.
codex mcp add colab-drive \
--env COLAB_MCP_ROOT="$HOME/notebooks" \
--env COLAB_MCP_DRIVE_ACCESS=file \
-- /absolute/path/to/colab-drive-mcp/.venv/bin/colab-drive-mcp
Add this server to the VS Code MCP configuration:
{
"servers": {
"colab-drive": {
"type": "stdio",
"command": "/absolute/path/to/colab-drive-mcp/.venv/bin/colab-drive-mcp",
"env": {
"COLAB_MCP_ROOT": "/absolute/path/to/notebooks",
"COLAB_MCP_DRIVE_ACCESS": "file"
}
}
}
}
Google Colab may add a metadata property to stream outputs. That property is
invalid under the standard nbformat v4 schema. During Drive downloads, this
server removes only that incompatible property. Stream text and all other
outputs are preserved.
COLAB_MCP_ROOT.authorize_google_drive call.file access unless full Drive discovery is required.This project is not affiliated with or endorsed by Google.
.venv/bin/pip install -e '.[drive,test]'
.venv/bin/pytest
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.