Discord Bot

This connector uses the Discord REST API v10 (https://discord.com/developers/docs).

Setup:

1. Open https://discord.com/developers/applications → New Application → name it (this becomes the app, not the bot).
2. Sidebar → Bot → Reset Token → copy the token. Treat as a secret — anyone with it can act as the bot.
3. Sidebar → Installation (or OAuth2 → URL Generator in older UI): pick scope bot, then permissions like Send Messages, Embed Links, Attach Files, Read Message History, Add Reactions, View Channels. Open the generated URL in a browser to install the bot into a server (you must be admin or have Manage Server). Repeat per server.
4. Set DISCORD_BOT_TOKEN to the token from step 2.

Authentication: header Authorization: Bot {{DISCORD_BOT_TOKEN}} — note the literal Bot prefix (NOT Bearer). The adapter sets this header via authType=API_KEY with the Authorization header name.

Snowflake IDs: every channel, guild, user, message in Discord is a numeric snowflake (~18-19 digits, string-typed). Discover them via discord_bot_list_guilds → discord_bot_list_guild_channels → drill down. In the Discord client, enable Developer Mode (User Settings → Advanced) and right-click any object → 'Copy ID' to grab snowflakes manually.

Channel types: 0=text, 2=voice, 4=category, 5=announcement, 11=public thread, 12=private thread, 13=stage, 15=forum. Messages can be sent to text (0), announcement (5), threads (11/12), forum posts (15 via thread).

Sending a message — embeds vs content:

• content: plain text (Markdown supported, ≤ 2000 chars).
• embeds: rich card with title/description/color/fields/image/timestamp (up to 10 per message, each ≤ 6000 chars total). Use embeds for structured data (release notes, alerts, dashboards).

File attachments: must be uploaded as multipart in the same request — NOT supported in a single tool call here. Workaround: host the file on a public URL and include it as an embed image or a hyperlink in the content. For attaching the file itself, do the multipart upload externally and pass the resulting message_id.

Threads vs channels: threads are child channels of a parent channel; the API treats them like channels (same endpoint /channels/{id}/messages). The thread_id IS the channel_id.

Rate limits: per-route AND global. Discord returns X-RateLimit-Remaining / X-RateLimit-Reset-After headers. On 429, wait the retry_after seconds. Hard cap: 50 req/sec global per token.

Permission errors (50001 / 50013): bot needs the right server permission in the channel. Adjust the bot's role permissions or grant per-channel overrides.

DMs to users: you can't DM a user out of the blue — you must first call discord_bot_create_dm_channel with the user_id to open a DM channel, then send to that channel_id. The user must also share at least one server with the bot.

Inbound / gateway / voice / slash commands: out of scope here. The Discord WebSocket gateway (for receiving messages, presence, voice) and Interactions endpoints (slash commands) need a long-running process or a registered interactions webhook — separate plan.