A
licenseB
qualityD
maintenanceLocal-first MCP server for controlling Google Colab as a development, shell, file, and training runtime, with tools for notebook editing, GPU acceleration, and file transfer.
59
8
Apache 2.0
colab-drive-mcp
Related Servers
Alternatives to colab-drive-mcp
No user-submitted related servers found.
Related Servers
- Apache 2.0
- AlicenseBqualityCmaintenanceAn MCP server that bridges local AI agents to Google Colab notebooks, enabling execution of Python code and interaction with notebook states directly from the agent.1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA local MCP server for reading, writing, and executing Jupyter notebooks using jupyter_client for direct kernel communication.-
- AlicenseNot gradedqualityDmaintenanceMCP server for Jupyter notebook navigation and editing. Reads .ipynb files directly as JSON, providing efficient tools for reading, searching, and modifying cells without needing a Jupyter server.MIT
- FlicenseAqualityCmaintenanceMCP server for structural editing of Jupyter notebook cells (list, read, insert, edit, patch, delete, move) without kernel execution.10-
TDQS
B3.3/5.0
Scored across 16 tools
Disambiguation5/5
Each tool targets a distinct action (e.g., add/delete/update cells, push/pull notebooks, authorization) with no overlapping functionality. Descriptions clearly differentiate between local and Drive operations.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., add_local_cell, list_drive_notebooks), making the API predictable and easy for agents to navigate.
Tool Count5/5
16 tools are well-scoped for managing local notebooks and Drive synchronization. The count covers core operations without unnecessary bloat.
Completeness4/5
The set covers local notebook management (CRUD cells, create notebook) and Drive sync (push, pull, copy, list). Minor gaps like missing delete_drive_notebook are acceptable given the focus on sync workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues