Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Colab Drive MCP

by YummyTastyCodeversion 0.1.3i★ –iRuns on your computer
Registry nameio.github.YummyTastyCode/colab-drive-mcp

Install

Overview

Description from the maker (original English)

Synchronize Colab notebook files through Google Drive without executing notebook code.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Docs, sheets & office work
  • You need to fill in: COLAB_MCP_ROOT

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: COLAB_MCP_ROOT, COLAB_MCP_DRIVE_ACCESS, COLAB_MCP_GOOGLE_CREDENTIALS, COLAB_MCP_GOOGLE_TOKEN

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "colab-drive": {
      "command": "uvx",
      "args": [
        "colab-drive-mcp"
      ],
      "env": {
        "COLAB_MCP_ROOT": "your-value",
        "COLAB_MCP_DRIVE_ACCESS": "your-value",
        "COLAB_MCP_GOOGLE_CREDENTIALS": "your-value",
        "COLAB_MCP_GOOGLE_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add colab-drive --env COLAB_MCP_ROOT=your-value --env COLAB_MCP_DRIVE_ACCESS=your-value --env COLAB_MCP_GOOGLE_CREDENTIALS=your-value --env COLAB_MCP_GOOGLE_TOKEN=your-value -- uvx colab-drive-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "colab-drive": {
      "command": "uvx",
      "args": [
        "colab-drive-mcp"
      ],
      "env": {
        "COLAB_MCP_ROOT": "your-value",
        "COLAB_MCP_DRIVE_ACCESS": "your-value",
        "COLAB_MCP_GOOGLE_CREDENTIALS": "your-value",
        "COLAB_MCP_GOOGLE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "colab-drive": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "colab-drive-mcp"
      ],
      "env": {
        "COLAB_MCP_ROOT": "your-value",
        "COLAB_MCP_DRIVE_ACCESS": "your-value",
        "COLAB_MCP_GOOGLE_CREDENTIALS": "your-value",
        "COLAB_MCP_GOOGLE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • COLAB_MCP_ROOT required env
    Absolute local directory that bounds notebook file access.
  • COLAB_MCP_DRIVE_ACCESS env
    Google Drive access mode: file for minimal access or full for discovering existing notebooks.
  • COLAB_MCP_GOOGLE_CREDENTIALS env
    Optional path to the local Google OAuth Desktop client JSON.
  • COLAB_MCP_GOOGLE_TOKEN env
    Optional path to the local Google OAuth token JSON.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account YummyTastyCode, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 2183 servers in this category
  • Published to the registry more recently than 13% of the other 2183 servers in this category
  • Basic checks equal to or better than 100% of the other 2183 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Colab Drive MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: COLAB_MCP_ROOT

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago
Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago
Install

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Colab Drive MCP

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 .ipynb files 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.

Features

  • Inspect and edit notebook cells without loading the entire notebook.
  • Create, search, copy, upload, and download notebooks.
  • Report live upload and download progress to MCP clients that request it.
  • Compare local and Drive notebook copies using Drive metadata and content MD5.
  • Keep local file access inside a configured root directory.
  • Normalize Colab-specific stream output metadata during downloads.
  • Diagnose Google Drive setup without unexpectedly opening a browser.
  • Return actionable errors for missing credentials, expired authorization, permissions, missing files, and rate limits.

Non-goals

  • Starting, controlling, or monitoring a Google Colab runtime.
  • Detecting whether a Colab runtime is connected, busy, or executing a file.
  • Executing notebook cells locally or remotely.
  • Browser automation, automatic Run all, or unattended Colab sessions.
  • Circumventing Colab quotas, idle timeouts, access controls, or usage policies.
  • Deploying or running the project contained inside a notebook.

AI Contract

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.

Tools

Setup
  • get_google_drive_status: diagnose dependencies, credentials, token, and scope.
  • authorize_google_drive: explicitly open the Google OAuth browser flow.
Local notebooks
  • list_local_notebooks, get_local_notebook, create_local_notebook
  • add_local_cell, update_local_cell, delete_local_cell
  • search_local_cells, clear_local_outputs
Google Drive
  • list_drive_notebooks, pull_drive_notebook, push_local_notebook
  • get_notebook_sync_status, copy_drive_notebook, get_colab_url

pull_drive_notebook and push_local_notebook synchronize notebook files. They send MCP progress notifications when the client supplies a progress token, but clients decide whether and how to display those notifications. They never execute notebook code. get_colab_url returns a URL but does not open a browser.

get_notebook_sync_status compares the local notebook's upload representation with Drive's MD5 checksum and returns in_sync, differs, remote_only, or unknown. It also returns Drive metadata such as modification time and version. It cannot determine whether Colab is currently executing the notebook because Google Drive does not expose Colab runtime activity.

Install

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

Google Drive Setup

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:

  1. Create a Google Cloud project.
  2. Enable the Google Drive API.
  3. Configure the OAuth consent screen and add your account as a test user.
  4. Create an OAuth Client ID with application type Desktop app.
  5. Download the JSON to ~/.config/colab-mcp/credentials.json.
  6. Call 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_CREDENTIALS
  • COLAB_MCP_GOOGLE_TOKEN

Never commit OAuth credentials or tokens.

Drive Access Modes

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 Configuration

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

VS Code Configuration

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" } } } }

Colab Compatibility

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.

Security

  • OAuth tokens stay on the local machine.
  • Local tools are restricted to COLAB_MCP_ROOT.
  • Authorization requires an explicit authorize_google_drive call.
  • Use file access unless full Drive discovery is required.
  • Review actions before overwriting an existing Drive file.

This project is not affiliated with or endorsed by Google.

Development

.venv/bin/pip install -e '.[drive,test]'

.venv/bin/pytest

Ask PopNx