discord
REST-first clone built for the bot workflows developers actually automate: reading guild state, managing channels and messages, running webhook flows, working with threads, and handling interaction responses.
Start here
| Question | Answer |
|---|---|
| Best for | Bot agents that moderate channels, reply in threads, handle webhooks, or respond to slash-command style interactions. |
| Connect with | Route mode for discord.com/api/v10, direct REST base URLs from archal clone start discord, or MCP where your harness uses Archal tools. |
| Known limits | The clone focuses on bot workflows. It is not a full Discord client UI or voice/media simulation. |
| Seeds | Common seeds: small-server, empty, harvested. See Seeds for usage. |
Available tools
| Group | Coverage |
|---|---|
| Identity | Bot user, application metadata |
| Guilds | Guild, role, member, and channel reads |
| Channels | Create, edit, delete, invite lifecycle |
| Messages | Create, edit, delete, bulk delete, reactions, pins |
| Webhooks | Create, execute, edit, delete, message lifecycle |
| Threads | Create, join, leave, member, archive |
| Commands | Guild command list, create, edit, delete, bulk overwrite |
| Interactions | Callback and original-response lifecycle after a captured invocation |
Notes
- Discord doesn’t expose an official MCP surface for bot operations, so the clone is REST-first. Test code typically talks to
discord.com/api/v10withfetch,discord.jsREST, or another HTTP client. - The clone enforces workflow semantics rather than literal fixture text. Custom seeds can rename channels, roles, and messages freely.
- Route-mode
archal/vitestis supported.