research: Colab REST API (v1beta runtimes/operations) as a control-plane adapter #12
Labels
No labels
area/backup
area/cli
area/docs
area/dsh
area/forgejo
area/host
area/mcp
area/plugin
area/security
area/ux
needs-operator
priority/later
priority/next
priority/now
type/bug
type/research
type/task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dsh-plugins/dsh-colab#12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Google documents the Colab API as a REST service as well as an MCP server:
https://developers.google.com/colab/api/reference/rest
Discovery documents:
https://colaboratory.googleapis.com/$discovery/rest?version=v1beta(andv1), plus OpenAPI 3.0.Surface (v1beta)
GET/POST /v1beta/runtimes,GET/DELETE /v1beta/runtimes/{name}GET /v1beta/runtimespecs(machine shapes + eligibility)GET /v1beta/{name=subscription}GET /v1/operations,GET /v1/operations/{name}:waitSame control plane the MCP server wraps. Unlike MCP it is a plain HTTP API with a stable discovery document; no MCP handshake, no OAuth-MCP setup. Unlike the CLI it still has no file transfer, no Drive mount, no attached exec / idle guard, so it cannot replace the run path.
Why note it
fetch) forlist_runtimes,runtimespecs,get_subscriptionif MCP auth is awkward on a host.colab_fanout(v1): list runtimes, match scheduler-owned tags, delete leftovers.Evaluation
Findings go into the new "Related: the Colab REST API" section of
docs/mcp-spike.md; roadmap has a later-ideas row.