diff --git a/external_plugins/colab/.mcp.json b/external_plugins/colab/.mcp.json
new file mode 100644
index 00000000..1acf54e1
--- /dev/null
+++ b/external_plugins/colab/.mcp.json
@@ -0,0 +1,9 @@
+{
+ "mcpServers": {
+ "colab-mcp": {
+ "command": "python",
+ "args": ["-m", "uv", "tool", "run", "git+https://github.com/googlecolab/colab-mcp"],
+ "timeout": 30000
+ }
+ }
+}
\ No newline at end of file
diff --git a/external_plugins/colab/.zcode-plugin/plugin.json b/external_plugins/colab/.zcode-plugin/plugin.json
new file mode 100644
index 00000000..1f0cd31c
--- /dev/null
+++ b/external_plugins/colab/.zcode-plugin/plugin.json
@@ -0,0 +1,26 @@
+{
+ "name": "colab",
+ "version": "0.1.2",
+ "description": "Google Colab integration for ZCode: the official colab-mcp browser-bridge MCP server plus a google-colab-cli command reference for provisioning Colab runtimes (CPU/GPU/TPU), executing code, and transferring files.",
+ "description_i18n": {
+ "en": "Google Colab integration for ZCode: the official colab-mcp browser-bridge MCP server plus a google-colab-cli command reference for provisioning Colab runtimes (CPU/GPU/TPU), executing code, and transferring files.",
+ "zh-CN": "面向 ZCode 的 Google Colab 集成:官方 colab-mcp 浏览器桥接 MCP 服务器,以及 google-colab-cli 命令参考——用于创建 Colab 运行时(CPU/GPU/TPU)、执行代码和传输文件。"
+ },
+ "author": {
+ "name": "movtigroup",
+ "url": "https://github.com/movtigroup"
+ },
+ "keywords": [
+ "colab",
+ "google-colab",
+ "colab-mcp",
+ "google-colab-cli",
+ "gpu",
+ "tpu",
+ "mcp",
+ "notebook",
+ "machine-learning"
+ ],
+ "skills": "./skills",
+ "mcpServers": "./.mcp.json"
+}
\ No newline at end of file
diff --git a/external_plugins/colab/LICENSE b/external_plugins/colab/LICENSE
new file mode 100644
index 00000000..d6456956
--- /dev/null
+++ b/external_plugins/colab/LICENSE
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/external_plugins/colab/NOTICE.md b/external_plugins/colab/NOTICE.md
new file mode 100644
index 00000000..d7e92a1b
--- /dev/null
+++ b/external_plugins/colab/NOTICE.md
@@ -0,0 +1,17 @@
+# NOTICE
+
+This repository is an independent ZCode plugin that integrates Google's official Colab tools. It is **not affiliated with, endorsed by, or sponsored by Google**.
+
+## Copyright
+
+Copyright 2026 **movtigroup**
+
+The original content of this repository (skills, manifests, documentation, scripts) is licensed under the Apache License 2.0 — see [LICENSE](LICENSE).
+
+## Upstream projects
+
+- **colab-mcp** — https://github.com/googlecolab/colab-mcp — Copyright 2026 Google Inc., Apache License 2.0.
+ This repository does not redistribute its source code; the MCP server is fetched directly from the official repository at runtime via `uvx`/`uv tool run`.
+
+- **google-colab-cli** — https://github.com/googlecolab/google-colab-cli — Copyright 2026 Google Inc., Apache License 2.0.
+ Referenced by documentation only; no source code is included.
diff --git a/external_plugins/colab/README.md b/external_plugins/colab/README.md
new file mode 100644
index 00000000..4eaaa01a
--- /dev/null
+++ b/external_plugins/colab/README.md
@@ -0,0 +1,196 @@
+
+
+# 🔬 Google Colab Tools for ZCode
+
+**Google Colab, inside your AI agent — powered by Google's official open-source tools, built independently.**
+
+A professional ZCode plugin integrating Google's official [colab-mcp](https://github.com/googlecolab/colab-mcp) browser-bridge MCP server and the [google-colab-cli](https://github.com/googlecolab/google-colab-cli) headless CLI — provision GPU/TPU runtimes, run code, and manage files on Google Colab without ever leaving your agent.
+
+[](LICENSE)
+[](CHANGELOG.md)
+[](.github/workflows/validate.yml)
+[](../../commits/main)
+[](../../stargazers)
+[](../../)
+[](README.md#-installation)
+[](scripts/)
+[](https://modelcontextprotocol.io)
+[](CONTRIBUTING.md)
+
+
+
+---
+
+## 📑 Table of Contents
+
+- [Overview](#-overview)
+- [How It Works](#-how-it-works)
+- [Repository Layout](#-repository-layout)
+- [Installation](#-installation)
+- [Quick Start](#-quick-start)
+- [Troubleshooting](#-troubleshooting)
+- [FAQ](#-faq)
+- [Development](#-development)
+- [Roadmap](#-roadmap)
+- [License & Notice](#-license--notice)
+- [Acknowledgments](#-acknowledgments)
+
+## 👁 Overview
+
+| | |
+|:---|:---|
+| 🌉 **Browser bridge** | Pair ZCode with a live Colab notebook open in your browser via Google's official MCP proxy — inspect kernel state, run cells, iterate with the agent |
+| ⚡ **Headless control** | Provision CPU/GPU/TPU sessions, execute scripts, upload/download artifacts with the official CLI — no browser required |
+| 🧠 **Two skills** | `colab-mcp` (pairing flow, dynamic tools, troubleshooting) and `colab-cli` (full command reference, agent workflows) |
+| 🛡 **No redistribution** | The MCP server is fetched at runtime from Google's official repo — this plugin ships configuration and expertise only |
+| 🌐 **Bilingual skills, English docs** | Skills are pre-optimized for agent use; all documentation is in English |
+| 🧪 **Validated** | 15-point repository validator runs locally and in CI on every push |
+
+## 🔄 How It Works
+
+```mermaid
+flowchart LR
+ subgraph local["🖥 Your machine"]
+ Z["ZCode agent"]
+ P["colab-mcp proxy
(uv tool run)"]
+ S["colab-cli
(WSL on Windows)"]
+ end
+ subgraph cloud["☁ Google"]
+ B["Colab notebook
in your browser"]
+ R["Colab runtime
CPU / GPU / TPU"]
+ end
+ Z <-- "MCP stdio" --> P
+ P <-- "local WebSocket + token" --> B
+ Z -- "shell" --> S
+ S --> R
+ B --> R
+```
+
+**Two independent paths:** the MCP proxy pairs ZCode with a notebook you control in the browser, while the CLI provisions raw runtimes for fully automated jobs.
+
+## 📁 Repository Layout
+
+```
+marketplace.json ← ZCode marketplace catalog
+LICENSE ← Apache-2.0 full text
+NOTICE.md ← legal notice (non-affiliation, attribution)
+CHANGELOG.md ← version history
+colab/
+├── .zcode-plugin/plugin.json ← plugin manifest (v0.1.2)
+├── .mcp.json ← official colab-mcp server definition
+└── skills/
+ ├── colab-mcp/SKILL.md ← browser pairing flow & troubleshooting
+ └── colab-cli/SKILL.md ← headless CLI command reference
+scripts/
+├── validate.py ← 15-point repository validator
+└── smoke_colab_mcp.py ← MCP handshake smoke test
+.github/workflows/validate.yml ← CI: validates the repo on push & PR
+```
+
+## 🚀 Installation
+
+1. In ZCode: **Plugin Marketplace → Add → Add Plugin Marketplace**
+2. Paste the repository URL: `https://github.com/movtigroup/Colab-Plugin.git`
+3. Install **Google Colab Tools** from the `movti-colab` marketplace
+4. Restart ZCode so the MCP server starts fresh
+
+### Requirements
+
+| Requirement | Why | Install |
+|---|---|---|
+| [uv](https://docs.astral.sh/uv/) | Runs the MCP server | `pip install uv` |
+| Google account | Access to colab.research.google.com | — |
+| WSL *(Windows only)* | `google-colab-cli` targets Linux/macOS | `wsl --install` |
+
+## ⚡ Quick Start
+
+**Browser pairing** — select the `colab-mcp` skill and say:
+
+> *"Connect me to Colab"*
+
+The pairing tool opens Colab in your browser; after you sign in and the notebook connects back over WebSocket, the notebook's tools appear dynamically.
+
+**Headless GPU job** — select the `colab-cli` skill:
+
+```bash
+colab new -s trainer --gpu A100 # provision a runtime
+colab install -s trainer torch transformers
+colab exec -s trainer -f train.py # run code (contents sent to kernel)
+colab download -s trainer checkpoints/model.bin ./model.bin
+colab stop -s trainer # release the VM
+```
+
+## 🌐 Network Access & Dependencies
+
+- **Network access**: `colab-mcp` starts a local WebSocket server and communicates with colab.research.google.com; `google-colab-cli` talks to the Google Colab API. At build time, uv fetches the official tools from PyPI and GitHub.
+- **Command execution**: the MCP server is launched via `python -m uv tool run`; the `colab-cli` skill guides the agent to run `colab` commands.
+- **File writes**: uv cache and Colab session metadata (`~/.config/colab-cli/`); `colab upload/download` reads and writes files on demand.
+- **Third-party code**: fetched at runtime from [googlecolab/colab-mcp](https://github.com/googlecolab/colab-mcp) and [googlecolab/google-colab-cli](https://github.com/googlecolab/google-colab-cli) — both Google Apache-2.0 projects; nothing is redistributed in this repository.
+- **Credentials**: none stored in the plugin; Google authorization happens in your browser session.
+
+## 🛠 Troubleshooting
+
+| Symptom | Fix |
+|---|---|
+| No Colab tools listed | Session not paired — invoke `open_colab_browser_connection`, keep the Colab tab open, and sign in to Google |
+| Server fails to start | `pip install uv`, then restart ZCode |
+| uvx build fails behind a mirror | Add `--index https://pypi.org/simple` to `.mcp.json` args |
+| Pairing times out | Invoke the pairing tool again for a fresh 60-second window |
+| colab-cli on Windows | Run inside WSL — Windows is not supported by the upstream CLI |
+
+## ❓ FAQ
+
+
+Is this made by Google?
+
+No. This is an independent integration of Google's official open-source tools — see [NOTICE.md](NOTICE.md).
+
+
+
+Where does the MCP server come from?
+
+It is fetched at runtime from googlecolab/colab-mcp via uv tool run. Nothing is redistributed here.
+
+
+
+Does it cost anything?
+
+The Colab free tier works. GPU/TPU accelerators and high-RAM shapes consume Colab compute points (Pro/Pro+).
+
+
+
+Why is the CLI Linux/macOS only?
+
+That is an upstream limitation of google-colab-cli, documented by Google. On Windows, run it inside WSL.
+
+
+## 🧪 Development
+
+```bash
+python scripts/validate.py # 15-point repo validation
+python scripts/smoke_colab_mcp.py # live MCP handshake + tools/list test
+```
+
+CI runs the validator on every push and pull request.
+
+## 🗺 Roadmap
+
+- [x] Plugin foundation: MCP server, pairing and CLI skills, marketplace catalog
+- [x] Professional packaging: license, notice, changelog, CI, validators
+- [ ] Tagged releases surfaced in the ZCode marketplace
+- [ ] Extra skills: Drive-mount workflows, compute-points monitoring
+
+## 📄 License & Notice
+
+Released under the [Apache License 2.0](LICENSE). Independent project — not affiliated with, endorsed by, or sponsored by Google. Legal details in [NOTICE.md](NOTICE.md), history in [CHANGELOG.md](CHANGELOG.md).
+
+## 🙏 Acknowledgments
+
+- [googlecolab/colab-mcp](https://github.com/googlecolab/colab-mcp) · © Google, Apache-2.0
+- [googlecolab/google-colab-cli](https://github.com/googlecolab/google-colab-cli) · © Google, Apache-2.0
+
+
+
+**⭐ Star this repo if it saves you a GPU trip to the browser!**
+
+
diff --git a/external_plugins/colab/README_CN.md b/external_plugins/colab/README_CN.md
new file mode 100644
index 00000000..e86ac686
--- /dev/null
+++ b/external_plugins/colab/README_CN.md
@@ -0,0 +1,130 @@
+# 面向 ZCode 的 Google Colab 工具
+
+**Google Colab,就在你的 AI 智能体中 — 由 Google 官方开源工具驱动,独立构建。**
+
+面向 ZCode 的专业 Google Colab 集成:整合 Google 官方 [colab-mcp](https://github.com/googlecolab/colab-mcp) 浏览器桥接 MCP 服务器与 [google-colab-cli](https://github.com/googlecolab/google-colab-cli) 无头 CLI — 在不离开智能体的情况下创建 GPU/TPU 运行时、执行代码并管理 Colab 上的文件。
+
+[](LICENSE)
+[](https://github.com/movtigroup/Colab-Plugin/releases)
+[](https://modelcontextprotocol.io)
+
+## 概览
+
+| | |
+|:---|:---|
+| 🌉 **浏览器桥接** | 通过 Google 官方 MCP 代理,将 ZCode 与你在浏览器中打开的 Colab 笔记本配对 — 检查内核状态、运行单元格、与智能体协作迭代 |
+| ⚡ **无头控制** | 使用官方 CLI 创建 CPU/GPU/TPU 会话、执行脚本、上传/下载产物 — 无需浏览器 |
+| 🧠 **两个技能** | `colab-mcp`(配对流程、动态工具、故障排除)与 `colab-cli`(完整命令参考、智能体工作流) |
+| 🛡 **不重新分发** | MCP 服务器在运行时从 Google 官方仓库获取 — 本插件仅提供配置与使用知识 |
+| 🌐 **双语文档** | 英文与中文文档齐备;技能针对智能体使用预先优化 |
+| 🧪 **经过验证** | 15 项仓库校验器在本地与 CI 中运行 |
+
+## 工作原理
+
+```mermaid
+flowchart LR
+ subgraph local["🖥 本机"]
+ Z["ZCode 智能体"]
+ P["colab-mcp 代理
(uv tool run)"]
+ S["colab-cli
(Windows 上经 WSL)"]
+ end
+ subgraph cloud["☁ Google"]
+ B["浏览器中的 Colab 笔记本"]
+ R["Colab 运行时
CPU / GPU / TPU"]
+ end
+ Z <-- "MCP stdio" --> P
+ P <-- "本地 WebSocket + 令牌" --> B
+ Z -- "shell" --> S
+ S --> R
+ B --> R
+```
+
+**两条独立路径:** MCP 代理将 ZCode 与你在浏览器中控制的笔记本配对;CLI 则为全自动化任务创建原始运行时。
+
+## 仓库布局
+
+```
+plugin.json / .mcp.json / skills/ ← 插件内容
+LICENSE (Apache-2.0) / NOTICE.md ← 许可与法律声明
+README.md / README_CN.md ← 双语文档
+scripts/ ← 校验器与 MCP 冒烟测试
+.github/workflows/ ← CI
+```
+
+## 安装
+
+在 ZCode 中:**Plugin Marketplace → Add → Add Plugin Marketplace**,粘贴本仓库 URL 并安装 **Google Colab Tools**,然后重启 ZCode。
+
+### 需求
+
+| 需求 | 原因 | 安装 |
+|---|---|---|
+| [uv](https://docs.astral.sh/uv/) | 运行 MCP 服务器 | `pip install uv` |
+| Google 账号 | 访问 colab.research.google.com | — |
+| WSL(仅 Windows) | google-colab-cli 仅支持 Linux/macOS | `wsl --install` |
+
+## 快速开始
+
+**浏览器配对** — 选择 `colab-mcp` 技能并说:
+
+> *"把我连接到 Colab"*
+
+配对工具会在浏览器中打开 Colab;登录且笔记本通过 WebSocket 连回本地代理后,笔记本的工具会动态出现。
+
+**无头 GPU 任务** — 选择 `colab-cli` 技能:
+
+```bash
+colab new -s trainer --gpu A100 # 创建运行时
+colab install -s trainer torch transformers
+colab exec -s trainer -f train.py # 运行代码(内容直接发送到内核)
+colab download -s trainer checkpoints/model.bin ./model.bin
+colab stop -s trainer # 释放虚拟机
+```
+
+## 网络访问与依赖 / Network access and dependencies
+
+- **网络访问**:`colab-mcp` 在本机启动 WebSocket 服务器并与 colab.research.google.com 通信;`google-colab-cli` 与 Google Colab API 通信。构建时 uv 会从 PyPI 与 GitHub 拉取官方工具。
+- **命令执行**:MCP 服务器通过 `python -m uv tool run` 启动;`colab-cli` 技能指导智能体执行 `colab` 命令。
+- **文件写入**:uv 缓存、Colab 会话元数据(`~/.config/colab-cli/`);`colab upload/download` 按需读写文件。
+- **第三方代码**:运行时从 [googlecolab/colab-mcp](https://github.com/googlecolab/colab-mcp) 与 [googlecolab/google-colab-cli](https://github.com/googlecolab/google-colab-cli) 获取,两者均为 Google 的 Apache-2.0 项目;本仓库不重新分发其源代码。
+- **凭证**:无需在插件内存储任何凭证;Google 授权发生在你的浏览器会话中。
+
+## 故障排除
+
+| 现象 | 解决方法 |
+|---|---|
+| 看不到 Colab 工具 | 会话尚未配对 — 调用 `open_colab_browser_connection`,保持 Colab 标签页打开并登录 Google |
+| 服务器启动失败 | `pip install uv`,然后重启 ZCode |
+| uvx 构建失败(镜像环境) | 在 `.mcp.json` 参数中添加 `--index https://pypi.org/simple` |
+| 配对超时 | 再次调用配对工具以获得新的 60 秒窗口 |
+| Windows 上的 colab-cli | 在 WSL 中运行 — 上游 CLI 不支持 Windows |
+
+## 常见问题
+
+
+这是 Google 的产品吗?
+
+不是。这是对 Google 官方开源工具的独立集成 — 见 NOTICE.md。
+
+
+
+MCP 服务器从哪里来?
+
+在运行时通过 uv tool run 从 googlecolab/colab-mcp 获取。此处不重新分发任何内容。
+
+
+
+有费用吗?
+
+Colab 免费层可用。GPU/TPU 加速器与高内存规格消耗 Colab 算力点数(Pro/Pro+)。
+
+
+
+为什么 CLI 仅限 Linux/macOS?
+
+这是 google-colab-cli 的上游限制。在 Windows 上请在 WSL 中运行。
+
+
+## 许可与声明
+
+基于 [Apache License 2.0](LICENSE) 发布。独立项目 — 与 Google 无隶属、未获认可或赞助。法律细节见 [NOTICE.md](NOTICE.md)。
diff --git a/external_plugins/colab/skills/colab-cli/SKILL.md b/external_plugins/colab/skills/colab-cli/SKILL.md
new file mode 100644
index 00000000..3d22bf34
--- /dev/null
+++ b/external_plugins/colab/skills/colab-cli/SKILL.md
@@ -0,0 +1,74 @@
+---
+name: colab-cli
+description: Use when the user wants headless/terminal control of Google Colab - provisioning CPU/GPU/TPU runtimes, running scripts on Colab VMs, uploading/downloading files, or automating pipelines with the official google-colab-cli. Also use when the user says "colab new", "colab exec", or asks to run heavy code on Colab GPUs without a browser notebook. Does not cover the browser-paired colab-mcp workflow - that is the colab-mcp skill.
+---
+
+# colab-cli — headless Colab from the terminal
+
+Official Google repo: https://github.com/googlecolab/google-colab-cli (Apache-2.0). The CLI controls
+Colab runtimes via Jupyter/WebSocket protocols; session metadata lives in
+`~/.config/colab-cli/sessions.json` (override with `--config`).
+
+## Requirements and platform
+
+- Install with `uv tool install google-colab-cli` (preferred) or `pip install google-colab-cli`.
+- **Windows is NOT officially supported** — upstream targets Linux/macOS and the supported
+ path on Windows is **WSL** (`wsl -d ` then use `colab` there; files stay in the
+ WSL filesystem for speed). Verified in practice (2026-11-05): the CLI installs via pip and
+ loads on Windows, and the OAuth flow initiates correctly — but full runtime behavior
+ (SSH tunnels, TTY console) is untested there, so prefer WSL for real work.
+- Accelerators: T4, L4, G4, H100, A100 GPUs; TPU v5e1/v6e1. High-RAM shapes require
+ Colab Pro/Pro+. L4/TPU shapes ignore `--high-mem`.
+- Auth strategies via global option `--auth {oauth2,adc}` (default `oauth2`): on first use
+ the CLI prints a Google OAuth URL and waits for the authorization code — every command
+ requires completing this flow once in an interactive terminal. ADC
+ (`--auth adc`) uses Application Default Credentials (e.g. `gcloud auth
+ application-default login`).
+
+## Command reference
+
+**Global flags**: `-s NAME` selects a named session for any command; `--auth {oauth2,adc}`.
+
+**Sessions**
+- `colab new [-s NAME] [--gpu T4|L4|G4|H100|A100] [--tpu ...] [--high-mem]` — provision a runtime
+- `colab sessions` — list sessions
+- `colab status [-s NAME]` — show session state / wait until ready
+- `colab url [-s NAME]`
+- `colab restart-kernel`, `colab stop [-s NAME]` — release the VM
+- `colab ssh [-s NAME]` — WebSocket shell, or OpenSSH ProxyCommand for IDEs
+
+**Execution**
+- For agent use, prefer `colab exec`: it transmits file contents directly to the kernel —
+ no manual upload needed.
+- `echo 'print(1)' | colab exec` — run code from stdin
+- `colab exec -f script.py [-s NAME]` — run a .py or .ipynb file
+- `colab run [--gpu T4] script.py [args...]` — ephemeral job: provisions VM, runs script, tears down
+- `colab repl` — interactive; `colab console` — tmux TTY shell
+
+**Files**
+- `colab upload [-s NAME] local remote` / `colab download [-s NAME] remote local`
+- `colab ls / rm / edit` — remote file management
+
+**Automation**
+- `colab install -s trainer torch transformers` — install packages (uv, pip fallback)
+- `colab log [-s NAME]` — export session log to .ipynb/.md/.txt/.jsonl
+- `colab usage`, `colab pay` — usage/compute points status
+- `colab drivemount` — mount Google Drive
+
+## Typical agent workflow (GPU job)
+
+```bash
+colab new -s trainer --gpu A100
+colab install -s trainer torch transformers
+colab exec -s trainer -f train.py
+colab download -s trainer checkpoints/model.bin ./model.bin
+colab stop -s trainer
+```
+
+## Agent tips
+
+- **Always `colab stop -s NAME` when done** — releases the VM so the user's compute points aren't drained by idle time.
+- `colab exec -f` sends file contents to the kernel (no upload step); use `colab upload/download` for artifacts like checkpoints.
+- Shebang trick for runnable GPU scripts:
+ `#!/usr/bin/env -S colab run --gpu L4 --keep`
+- For interactive/inspect workflows in a notebook the user has open in their browser, prefer the [[colab-mcp]] skill instead.
diff --git a/external_plugins/colab/skills/colab-mcp/SKILL.md b/external_plugins/colab/skills/colab-mcp/SKILL.md
new file mode 100644
index 00000000..7d71cb88
--- /dev/null
+++ b/external_plugins/colab/skills/colab-mcp/SKILL.md
@@ -0,0 +1,58 @@
+---
+name: colab-mcp
+description: Use when the user wants ZCode to interact with a live Google Colab notebook through the official colab-mcp server (run/inspect cells, use the notebook's kernel state, work inside the user's browser Colab session). Covers pairing ZCode with a browser Colab session, the dynamic tool list, and troubleshooting. Does not cover the headless google-colab-cli workflow - that is the colab-cli skill.
+---
+
+# colab-mcp — pairing ZCode with a browser Colab session
+
+Official Google repo: https://github.com/googlecolab/colab-mcp (Apache-2.0).
+
+## What this server is
+
+`colab-mcp` is a **local proxy MCP server**: it bridges the ZCode MCP client to a
+Google Colab notebook open in the user's browser. It is NOT a remote/HTTP MCP server —
+it must run on the user's device. When connected, the Colab notebook frontend pushes its
+own set of notebook tools through the proxy, so the tool list is **dynamic** and only
+appears after pairing.
+
+## Requirements
+
+- The plugin's `.mcp.json` launches the server as
+ `python -m uv tool run git+https://github.com/googlecolab/colab-mcp` (equivalent to
+ `uvx git+...`; chosen so it works even when uv's Scripts dir is not on PATH). It needs
+ the `uv` package importable by `python` (`pip install uv`). If a non-default package
+ index is configured (e.g. a mirror), add `--index https://pypi.org/simple` to the args
+ if the build fails.
+- ZCode supports `notifications/tools/list_changed`, which the server requires.
+- The user must be able to open colab.research.google.com in a browser and be signed in
+ to their Google account.
+
+## Pairing flow (do this whenever Colab tools are empty)
+
+1. Check whether Colab tools are present. If the `colab-mcp` server is connected but no
+ notebook tools are listed, the session is not paired yet.
+2. Call the injected tool `open_colab_browser_connection`.
+3. The tool opens the browser at
+ `https://colab.research.google.com/notebooks/empty.ipynb#mcpProxyToken=...&mcpProxyPort=...`
+ (token+port are URL fragments). The Colab frontend then connects back to the local
+ WebSocket server. The server waits up to 60 seconds for the handshake.
+4. Tell the user: keep the Colab tab open; sign in to Google if prompted; if the notebook
+ asks to connect/execute, connect to a runtime.
+5. After the connection lands, the server fires `tools/list_changed` — re-list the tools
+ and use them. If nothing lands within the window, call the tool again.
+
+## Troubleshooting
+
+- **No Colab tools / server has only the pairing tool**: not paired yet — run the pairing
+ flow above. Keep the tab open or it disconnects (the proxy notifies again when it drops).
+- **Server fails to start / `python -m uv` missing**: `pip install uv`, then restart ZCode
+ so the MCP server starts fresh.
+- **Build failed while uvx pulled the package**: if a mirror index is configured, try
+ args `["git+https://github.com/googlecolab/colab-mcp", "--index", "https://pypi.org/simple"]`
+ in the plugin's `.mcp.json`.
+- **Browser opened but no connection**: the user must be logged into
+ colab.research.google.com; corporate blockers can kill WebSockets to localhost.
+ Call `open_colab_browser_connection` again to re-open with a fresh token.
+- **Remote/headless work**: if the user wants code run without a browser session (e.g.
+ provision a GPU VM and run a script), use the headless CLI instead — see the
+ [[colab-cli]] skill.
diff --git a/marketplace.json b/marketplace.json
index c7f09a06..e3c29547 100644
--- a/marketplace.json
+++ b/marketplace.json
@@ -1443,6 +1443,47 @@
"mcp",
"verification"
]
+ },
+ {
+ "name": "colab",
+ "displayName": "Google Colab Tools",
+ "displayName_i18n": {
+ "en": "Google Colab Tools",
+ "zh-CN": "Google Colab 工具"
+ },
+ "source": "./external_plugins/colab",
+ "description": "Google Colab integration for ZCode: the official colab-mcp browser-bridge MCP server plus a google-colab-cli command reference for provisioning Colab runtimes (CPU/GPU/TPU), executing code, and transferring files.",
+ "description_i18n": {
+ "en": "Google Colab integration for ZCode: the official colab-mcp browser-bridge MCP server plus a google-colab-cli command reference for provisioning Colab runtimes (CPU/GPU/TPU), executing code, and transferring files.",
+ "zh-CN": "面向 ZCode 的 Google Colab 集成:官方 colab-mcp 浏览器桥接 MCP 服务器,以及 google-colab-cli 命令参考——用于创建 Colab 运行时(CPU/GPU/TPU)、执行代码和传输文件。"
+ },
+ "version": "0.1.2",
+ "author": {
+ "name": "movtigroup",
+ "url": "https://github.com/movtigroup"
+ },
+ "category": "developer-tools",
+ "keywords": [
+ "colab",
+ "google-colab",
+ "colab-mcp",
+ "google-colab-cli",
+ "gpu",
+ "tpu",
+ "mcp",
+ "notebook",
+ "machine-learning"
+ ],
+ "examplePrompts": [
+ "Connect me to Google Colab and run a quick PyTorch GPU sanity check",
+ "Provision an A100 Colab runtime, run training.py on it, and download the checkpoints"
+ ],
+ "examplePrompts_i18n": {
+ "zh-CN": [
+ "把我连接到 Google Colab,并跑一个快速的 PyTorch GPU 冒烟测试",
+ "创建一个 A100 Colab 运行时,在上面运行 training.py,然后下载 checkpoint"
+ ]
+ }
}
]
}
\ No newline at end of file