Google Workspace clone

Gmail, Calendar, Drive, Sheets, and Admin Directory stubs. Error responses use recorded fixture shapes — no live API calls.

Clone ID: google-workspace · Tier: fixture · Binary: clones-fixture

Start here

Question	Answer
Best for	Agents that read email, schedule meetings, inspect Drive files, or update sheets.
Connect with	Route mode for `Google API domains (configure route mode)`, REST at `{base}/google-workspace/api/...`, hosted `https://{sessionId}.clones.molar.it/google-workspace/api`, or MCP `molar_clone_spawn`
Known limits	Recorded responses only; unimplemented paths return `501`; read-only by default unless promoted stateful
Seeds	`assistant-baseline`, `calendar-packed-week`, `draft-send-cleanup`, `empty`, `gmail-busy-inbox` — apply on spawn or via `molar_clone_seed`

MCP tools

Fixture clones use shared control-plane tools — no vendor-specific MCP surface.

Tool	Description
`molar_clone_spawn`	Spawn fixture session (`kind: "google-workspace"`, optional `seed`)
`molar_clone_seed`	Apply a named seed to an existing session
`molar_clone_route`	Map `Google API domains (configure route mode)` to the active session
`molar_clone_stop`	Tear down the session

See MCP server for world_snapshot, world_restore, and cross-clone tools.

REST API coverage

The clone handles these recorded endpoints (local base http://localhost:8000/google-workspace/api):

GET /admin/directory/v1/users
GET /calendar/v3/calendars/primary/events
GET /calendar/v3/calendars/primary/events/evt_001
GET /calendar/v3/users/me/calendarList
GET /drive/v3/files
GET /gmail/v1/users/me/messages
GET /gmail/v1/users/me/messages/msg_abc123
GET /gmail/v1/users/me/profile
GET /gmail/v1/users/me/threads
GET /gmail/v1/users/me/threads/thread_xyz789
GET /sheets/v4/spreadsheets/sheet_abc123/values/Sheet1
POST /calendar/v3/calendars/primary/events
POST /calendar/v3/freeBusy
POST /gmail/v1/users/me/messages/send

If your agent calls a path not in this list, the clone returns 501 unimplemented_in_clone and logs the request. Submit missing coverage via the dashboard Developers → 501 request form.

Seeds

Seed	When to use
`assistant-baseline`	Starting state for assistant baseline scenarios
`calendar-packed-week`	Starting state for calendar packed week scenarios
`draft-send-cleanup`	Starting state for draft send cleanup scenarios
`empty`	Starting state for minimal / blank workspace scenarios
`gmail-busy-inbox`	Starting state for gmail busy inbox scenarios

molar clones spawn google-workspace --seed assistant-baseline

Connect

Mode	URL pattern
Local REST	`http://localhost:8000/google-workspace/api{path}`
Hosted REST	`https://{sessionId}.clones.molar.it/google-workspace/api{path}`
Route mode	Point `Google API domains (configure route mode)` at the clone via `molar_clone_route`
Dashboard	Clones explorer — filter by `google-workspace`

Set MOLAR_CLONE_GOOGLE_WORKSPACE_URL for BYOC fleets.

See Fixture clones overview and API & SDK.

GitLab HubSpot