GitHub clone

Repos, issues, pull requests, Actions, and search.

GitHub clone

Repos, issues, pull requests, Actions, and search. Error responses use recorded fixture shapes — no live API calls.

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

Start here

QuestionAnswer
Best forDev agents that triage issues, review PRs, search code, or inspect CI runs.
Connect withRoute mode for api.github.com, REST at {base}/github/api/..., hosted https://{sessionId}.clones.molar.it/github/api, or MCP molar_clone_spawn
Known limitsRecorded responses only; unimplemented paths return 501; read-only by default unless promoted stateful
Seedsci-cd-pipeline, empty, enterprise-repo, large-backlog, merge-conflict, permissions-denied, rate-limited, small-project, stale-issues — 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: "github", optional seed)
molar_clone_seedApply a named seed to an existing session
molar_clone_routeMap api.github.com 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/github/api):

  • DELETE /repos/molar/test-repo/git/refs/heads/stale-branch
  • GET /repos/molar/test-repo
  • GET /repos/molar/test-repo/actions/runs
  • GET /repos/molar/test-repo/actions/runs/5001
  • GET /repos/molar/test-repo/branches
  • GET /repos/molar/test-repo/commits
  • GET /repos/molar/test-repo/contents/README.md
  • GET /repos/molar/test-repo/issues
  • GET /repos/molar/test-repo/issues/42
  • GET /repos/molar/test-repo/pulls
  • GET /repos/molar/test-repo/pulls/7
  • GET /repos/molar/test-repo/pulls/7/comments
  • GET /repos/molar/test-repo/pulls/7/commits
  • GET /repos/molar/test-repo/pulls/7/files
  • GET /repos/molar/test-repo/pulls/7/files?view=files
  • GET /repos/molar/test-repo/pulls/7/reviews
  • GET /repos/molar/test-repo/pulls/7/status
  • GET /search/code
  • GET /search/issues
  • GET /search/repositories
  • GET /search/users
  • PATCH /repos/molar/test-repo/issues/42
  • PATCH /repos/molar/test-repo/pulls/7
  • POST /repos/molar/test-repo/forks
  • POST /repos/molar/test-repo/git/commits
  • POST /repos/molar/test-repo/git/refs
  • POST /repos/molar/test-repo/issues
  • POST /repos/molar/test-repo/issues/42/comments
  • POST /repos/molar/test-repo/pulls
  • POST /repos/molar/test-repo/pulls/7/reviews
  • POST /user/repos
  • PUT /repos/molar/test-repo/contents/src/main.go
  • PUT /repos/molar/test-repo/pulls/7/merge
  • PUT /repos/molar/test-repo/pulls/7/update-branch

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
ci-cd-pipelineStarting state for ci cd pipeline scenarios
emptyStarting state for minimal / blank workspace scenarios
enterprise-repoStarting state for enterprise repo scenarios
large-backlogStarting state for large backlog scenarios
merge-conflictStarting state for merge conflict scenarios
permissions-deniedStarting state for permissions denied scenarios
rate-limitedStarting state for rate limited scenarios
small-projectStarting state for small project scenarios
stale-issuesStarting state for stale issues scenarios
molar clones spawn github --seed ci-cd-pipeline

Connect

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

Set MOLAR_CLONE_GITHUB_URL for BYOC fleets.

See Fixture clones overview and API & SDK.