Jira clone

Issues, agile boards, sprints, JQL search, and service desk.

Jira clone

Issues, agile boards, sprints, JQL search, and service desk. Error responses use recorded fixture shapes — no live API calls.

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

Start here

QuestionAnswer
Best forIssue-triage agents, sprint planners, and JQL-based backlog queries.
Connect withRoute mode for *.atlassian.net, REST at {base}/jira/api/..., hosted https://{sessionId}.clones.molar.it/jira/api, or MCP molar_clone_spawn
Known limitsRecorded responses only; unimplemented paths return 501; read-only by default unless promoted stateful
Seedsempty, enterprise, large-backlog, small-project, sprint-active — apply on spawn or via molar_clone_seed

MCP tools

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

ToolDescription
molar_clone_spawnSpawn fixture session (kind: "jira", optional seed)
molar_clone_seedApply a named seed to an existing session
molar_clone_routeMap *.atlassian.net to the active session
molar_clone_stopTear 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/jira/api):

  • DELETE /rest/api/3/issue/MOLAR-103
  • DELETE /rest/api/3/issueLink/10001
  • GET /rest/agile/1.0/board
  • GET /rest/agile/1.0/board/1/issue
  • GET /rest/agile/1.0/board/1/sprint
  • GET /rest/agile/1.0/sprint/1/issue
  • GET /rest/api/2/project/PROJ
  • GET /rest/api/3/field/search
  • GET /rest/api/3/issue/MOLAR-101
  • GET /rest/api/3/issue/MOLAR-101/attachment
  • GET /rest/api/3/issue/MOLAR-101/development
  • GET /rest/api/3/issue/MOLAR-101/transitions
  • GET /rest/api/3/issue/MOLAR-101/worklog
  • GET /rest/api/3/issue/MOLAR-101?fields=created,updated,resolutiondate
  • GET /rest/api/3/issueLinkType
  • GET /rest/api/3/project
  • GET /rest/api/3/project/MOLAR/issue
  • GET /rest/api/3/project/MOLAR/versions
  • GET /rest/api/3/search
  • GET /rest/api/3/user
  • GET /rest/servicedesk/1/request/MOLAR-101/sla
  • POST /rest/agile/1.0/sprint
  • POST /rest/api/3/issue
  • POST /rest/api/3/issue/MOLAR-101/comment
  • POST /rest/api/3/issue/MOLAR-101/remotelink
  • POST /rest/api/3/issue/MOLAR-101/transitions
  • POST /rest/api/3/issue/MOLAR-101/worklog
  • POST /rest/api/3/issue/bulk
  • POST /rest/api/3/issue/bulk/changelog
  • POST /rest/api/3/issue/bulk/development
  • POST /rest/api/3/issueLink
  • POST /rest/api/3/version
  • POST /rest/api/3/version/bulk
  • PUT /rest/agile/1.0/sprint/3
  • PUT /rest/api/3/issue/MOLAR-101
  • PUT /rest/api/3/issue/MOLAR-101
  • PUT /rest/api/3/issue/MOLAR-101/comment/30001

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

SeedWhen to use
emptyStarting state for minimal / blank workspace scenarios
enterpriseStarting state for enterprise scenarios
large-backlogStarting state for large backlog scenarios
small-projectStarting state for small project scenarios
sprint-activeStarting state for sprint active scenarios
molar clones spawn jira --seed enterprise

Connect

ModeURL pattern
Local RESThttp://localhost:8000/jira/api{path}
Hosted RESThttps://{sessionId}.clones.molar.it/jira/api{path}
Route modePoint *.atlassian.net at the clone via molar_clone_route
DashboardClones explorer — filter by jira

Set MOLAR_CLONE_JIRA_URL for BYOC fleets.

See Fixture clones overview and API & SDK.