Supabase clone

Management API — projects, branches, migrations, functions, advisors.

Supabase clone

Management API — projects, branches, migrations, functions, advisors. Error responses use recorded fixture shapes — no live API calls.

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

Start here

QuestionAnswer
Best forPlatform agents that manage Supabase projects, branches, migrations, or edge functions.
Connect withRoute mode for api.supabase.com, REST at {base}/supabase/api/..., hosted https://{sessionId}.clones.molar.it/supabase/api, or MCP molar_clone_spawn
Known limitsRecorded responses only; unimplemented paths return 501; read-only by default unless promoted stateful
Seedsbulk-user-deletion, ecommerce, edge-cases, empty, feature-flag-override-mismatch, fired-employee-access, migration-poisoned-comment, rls-bypass-migration, saas-starter, small-project, vaultline-ecommerce — 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: "supabase", optional seed)
molar_clone_seedApply a named seed to an existing session
molar_clone_routeMap api.supabase.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/supabase/api):

  • DELETE /v1/projects/proj_def456/branches/branch_002
  • GET /v1/organizations
  • GET /v1/organizations/org_abc123
  • GET /v1/projects
  • GET /v1/projects/proj_def456
  • GET /v1/projects/proj_def456
  • GET /v1/projects/proj_def456/advisors
  • GET /v1/projects/proj_def456/api-keys
  • GET /v1/projects/proj_def456/branches
  • GET /v1/projects/proj_def456/database/extensions
  • GET /v1/projects/proj_def456/database/migrations
  • GET /v1/projects/proj_def456/database/tables
  • GET /v1/projects/proj_def456/functions
  • GET /v1/projects/proj_def456/functions/func_001
  • GET /v1/projects/proj_def456/logs
  • GET /v1/search/docs
  • POST /v1/projects
  • POST /v1/projects/proj_def456/branches
  • POST /v1/projects/proj_def456/branches/branch_001/merge
  • POST /v1/projects/proj_def456/branches/branch_001/rebase
  • POST /v1/projects/proj_def456/branches/branch_001/reset
  • POST /v1/projects/proj_def456/database/migrations
  • POST /v1/projects/proj_def456/database/query
  • POST /v1/projects/proj_def456/database/types
  • POST /v1/projects/proj_def456/functions/deploy
  • POST /v1/projects/proj_def456/pause
  • POST /v1/projects/proj_def456/restore

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
bulk-user-deletionStarting state for bulk user deletion scenarios
ecommerceStarting state for ecommerce scenarios
edge-casesStarting state for edge cases scenarios
emptyStarting state for minimal / blank workspace scenarios
feature-flag-override-mismatchStarting state for feature flag override mismatch scenarios
fired-employee-accessStarting state for fired employee access scenarios
migration-poisoned-commentStarting state for migration poisoned comment scenarios
rls-bypass-migrationStarting state for rls bypass migration scenarios
saas-starterStarting state for saas starter scenarios
small-projectStarting state for small project scenarios
vaultline-ecommerceStarting state for vaultline ecommerce scenarios
molar clones spawn supabase --seed bulk-user-deletion

Connect

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

Set MOLAR_CLONE_SUPABASE_URL for BYOC fleets.

See Fixture clones overview and API & SDK.