Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/googlecolab/colab-mcp/llms.txt

Use this file to discover all available pages before exploring further.

colab-mcp is normally started automatically by your MCP client when it reads your mcp.json configuration, so you rarely need to invoke it by hand. However, you can also run it directly from the terminal for debugging or scripting purposes, and every flag that controls its behavior can be passed either on the command line or through the args array in your MCP client config.

​
Basic invocation

uvx git+https://github.com/googlecolab/colab-mcp [options]

​
Flags

​
-l / --log
string
default:"<system temp dir>/colab-mcp-logs-*"
Directory to write log files into. When this flag is omitted, colab-mcp automatically creates a uniquely named directory under the system temp directory (e.g. /tmp/colab-mcp-logs-abc123 on Linux/macOS). Provide an explicit path if you want logs to land in a stable, predictable location.
​
-p / --enable-proxy
boolean
default:"true"
Enable the runtime proxy that bridges MCP tool calls through to the live Colab session running in your browser. The proxy is always enabled in the current implementation: the argument parser sets default=True and uses action="store_true", so passing --enable-proxy explicitly is a no-op and there is no flag to turn it off. This flag is reserved for a future disable mechanism.

​
Usage examples

​
Custom log directory

uvx git+https://github.com/googlecolab/colab-mcp --log /tmp/my-colab-logs

​
Specifying flags in mcp.json

You can pass any CLI flag via the args array in your MCP client configuration. The following example writes logs to a fixed path: 
{
  "mcpServers": {
    "colab-mcp": {
      "command": "uvx",
      "args": ["git+https://github.com/googlecolab/colab-mcp", "--log", "/tmp/colab-logs"],
      "timeout": 30000
    }
  }
}
Log files are named after the time the server process started, using the pattern colab-mcp.YYYY-MM-DD_HH-MM-SS.log. This makes it easy to correlate a log file with a particular agent session when you have multiple runs stored in the same directory.

Build docs developers (and LLMs) love

Get started for freeTalk to us