Discord clone

Bot identity, guild channels, messages, threads, and interactions.

Discord clone

Bot identity, guild channels, messages, threads, and interactions. Error responses use recorded fixture shapes — no live API calls.

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

Start here

QuestionAnswer
Best forDiscord bots that post messages, read channel history, and handle interactions.
Connect withRoute mode for api.discord.com, REST at {base}/discord/api/..., hosted https://{sessionId}.clones.molar.it/discord/api, or MCP molar_clone_spawn
Known limitsRecorded responses only; unimplemented paths return 501; read-only by default unless promoted stateful
Seedsempty, harvested, small-server — 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: "discord", optional seed)
molar_clone_seedApply a named seed to an existing session
molar_clone_routeMap api.discord.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/discord/api):

  • GET /v10/applications/@me
  • GET /v10/channels/111111111111111111/messages
  • GET /v10/guilds/123456789012345678
  • GET /v10/guilds/123456789012345678/channels
  • GET /v10/users/876543210987654321
  • POST /v10/channels/111111111111111111/messages
  • POST /v10/channels/111111111111111111/threads
  • POST /v10/guilds/123456789012345678/webhooks
  • POST /v10/interactions/interaction_aaa/123456/callback

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
harvestedStarting state for harvested scenarios
small-serverStarting state for small server scenarios
molar clones spawn discord --seed harvested

Connect

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

Set MOLAR_CLONE_DISCORD_URL for BYOC fleets.

See Fixture clones overview and API & SDK.