ClickUp clone

Workspace, folder, list, and task hierarchy stubs. Error responses use recorded fixture shapes — no live API calls.

Clone ID: clickup · Tier: fixture · Binary: clones-fixture

Start here

Question	Answer
Best for	PM automations that navigate teams, spaces, folders, lists, and tasks.
Connect with	Route mode for `api.clickup.com`, REST at `{base}/clickup/api/...`, hosted `https://{sessionId}.clones.molar.it/clickup/api`, or MCP `molar_clone_spawn`
Known limits	Recorded responses only; unimplemented paths return `501`; read-only by default unless promoted stateful
Seeds	`empty` — 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: "clickup"`, optional `seed`)
`molar_clone_seed`	Apply a named seed to an existing session
`molar_clone_route`	Map `api.clickup.com` 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/clickup/api):

GET /v2/folder/folder_789/list
GET /v2/list/list_456/task
GET /v2/space/space_abc123/folder
GET /v2/task/task_clickup_789
GET /v2/team
POST /v2/task

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
`empty`	Starting state for minimal / blank workspace scenarios

molar clones spawn clickup --seed empty

Connect

Mode	URL pattern
Local REST	`http://localhost:8000/clickup/api{path}`
Hosted REST	`https://{sessionId}.clones.molar.it/clickup/api{path}`
Route mode	Point `api.clickup.com` at the clone via `molar_clone_route`
Dashboard	Clones explorer — filter by `clickup`

Set MOLAR_CLONE_CLICKUP_URL for BYOC fleets.

See Fixture clones overview and API & SDK.

Cal.com Discord