Slack clone

Post messages, channel history, threads, users, and reactions. Error responses use recorded fixture shapes — no live API calls.

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

Start here

Question	Answer
Best for	Incident and comms bots that post updates, read history, or add reactions.
Connect with	Route mode for `slack.com`, REST at `{base}/slack/api/...`, hosted `https://{sessionId}.clones.molar.it/slack/api`, or MCP `molar_clone_spawn`
Known limits	Recorded responses only; unimplemented paths return `501`; read-only by default unless promoted stateful
Seeds	`busy-workspace`, `empty`, `engineering-team`, `incident-active` — 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: "slack"`, optional `seed`)
`molar_clone_seed`	Apply a named seed to an existing session
`molar_clone_route`	Map `slack.com` 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/slack/api):

GET /conversations.history
GET /conversations.list
GET /conversations.replies
GET /users.list
GET /users.profile.get
POST /chat.postMessage
POST /chat.postMessage?thread_ts=1717000000.000100
POST /reactions.add

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-workspace`	Starting state for busy workspace scenarios
`empty`	Starting state for minimal / blank workspace scenarios
`engineering-team`	Starting state for engineering team scenarios
`incident-active`	Starting state for incident active scenarios

molar clones spawn slack --seed busy-workspace

Connect

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

Set MOLAR_CLONE_SLACK_URL for BYOC fleets.

See Fixture clones overview and API & SDK.

Sentry Supabase