Linear clone

Issues, projects, initiatives, cycles, and teams. Error responses use recorded fixture shapes — no live API calls.

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

Start here

Question	Answer
Best for	Engineering agents that create or update issues, search backlogs, or manage projects.
Connect with	Route mode for `api.linear.app`, REST at `{base}/linear/api/...`, hosted `https://{sessionId}.clones.molar.it/linear/api`, or MCP `molar_clone_spawn`
Known limits	Recorded responses only; unimplemented paths return `501`; read-only by default unless promoted stateful
Seeds	`busy-backlog`, `empty`, `engineering-org`, `multi-team`, `small-team` — 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: "linear"`, optional `seed`)
`molar_clone_seed`	Apply a named seed to an existing session
`molar_clone_route`	Map `api.linear.app` 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/linear/api):

DELETE /v1/initiatives/init_001
GET /v1/comments
GET /v1/cycles
GET /v1/cycles/active
GET /v1/initiatives
GET /v1/initiatives/init_001
GET /v1/initiatives/init_001/projects
GET /v1/issueLabels
GET /v1/issues
GET /v1/issues
GET /v1/issues/issue_001
GET /v1/issues/issue_001/history
GET /v1/issues/issue_7h8i9j0k1l
GET /v1/issues/search
GET /v1/organizations
GET /v1/projects
GET /v1/projects
GET /v1/projects/proj_001/issues
GET /v1/teams
GET /v1/teams
GET /v1/users
GET /v1/viewer
GET /v1/workflowStates
PATCH /v1/initiatives/init_001
PATCH /v1/initiatives/init_001/archive
PATCH /v1/initiatives/init_001/unarchive
PATCH /v1/issues/issue_001
PATCH /v1/issues/issue_001
PATCH /v1/issues/issue_001
PATCH /v1/issues/issue_001
PATCH /v1/issues/issue_001
PATCH /v1/issues/issue_001
PATCH /v1/issues/issue_001
PATCH /v1/issues/issue_001/archive
PATCH /v1/issues/issue_001/subscribe
PATCH /v1/issues/issue_001/transfer
PATCH /v1/projects/proj_001
PATCH /v1/projects/proj_001
PATCH /v1/projects/proj_001
POST /v1/comments
POST /v1/initiatives
POST /v1/issueRelations
POST /v1/issues
POST /v1/issues/issue_001/duplicate
POST /v1/issues/issue_001/subtask
POST /v1/projects

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
`busy-backlog`	Starting state for busy backlog scenarios
`empty`	Starting state for minimal / blank workspace scenarios
`engineering-org`	Starting state for engineering org scenarios
`multi-team`	Starting state for multi team scenarios
`small-team`	Starting state for small team scenarios

molar clones spawn linear --seed busy-backlog

Connect

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

Set MOLAR_CLONE_LINEAR_URL for BYOC fleets.

See Fixture clones overview and API & SDK.

Jira OwnerRez