Automate Discord Messages and Roles

This skill automates Discord operations through Composio's Discord and Discordbot toolkits via Rube MCP (https://rube.app/mcp, no API keys needed). Prerequisites: Rube MCP connected with RUBE_SEARCH_TOOLS available, an active Discord connection via RUBE_MANAGE_CONNECTIONS with toolkit discordbot (bot operations, preferred for automation) or discord (user OAuth operations), completed via the returned auth link if not yet ACTIVE.

Its core workflows: sending messages (list the bot's guilds and a guild's channels, then DISCORDBOT_CREATE_MESSAGE with content up to 2000 characters or rich embed objects, optionally DISCORDBOT_UPDATE_MESSAGE to edit) - noting the bot needs SEND_MESSAGES permission, only the sending bot can edit its own messages, and high-frequency sends must respect Retry-After rate-limit headers; sending direct messages (DISCORDBOT_CREATE_DM to get or create the DM channel, then DISCORDBOT_CREATE_MESSAGE) - noting users with DMs disabled or who've blocked the bot can't be reached, and CREATE_DM returns the existing channel if one already exists; managing roles (DISCORDBOT_CREATE_GUILD_ROLE, DISCORDBOT_ADD_GUILD_MEMBER_ROLE, DISCORDBOT_DELETE_GUILD_ROLE, DISCORDBOT_GET_GUILD_MEMBER, DISCORDBOT_UPDATE_GUILD_MEMBER) - noting role assignment requires MANAGE_ROLES permission, the target role must sit lower than the bot's highest role in the hierarchy, and deletion permanently removes the role from all members; managing webhooks (listing, DISCORDBOT_CREATE_WEBHOOK, DISCORDBOT_EXECUTE_WEBHOOK, DISCORDBOT_UPDATE_WEBHOOK) - noting webhook tokens are secrets requiring secure handling, webhooks can post with a custom username/avatar per message, and creation requires MANAGE_WEBHOOKS permission; and managing reactions (listing users who reacted, deleting all/specific-emoji/specific-user reactions) - noting Unicode emojis must be URL-encoded while custom emojis use name:id format, and bulk deletion requires MANAGE_MESSAGES permission.

Common patterns: Discord uses 64-bit snowflake IDs as strings for all entities (guilds, channels, users, roles, messages, webhooks); permissions combine as bitwise OR values (SEND_MESSAGES = 0x800, MANAGE_ROLES = 0x10000000, MANAGE_MESSAGES = 0x2000, ADMINISTRATOR = 0x8); and most list endpoints support limit/before/after pagination, with messages and reactions capped at 100 per request. Known pitfalls: the discordbot toolkit uses bot tokens while discord uses user OAuth (bot preferred for automation), and Discord enforces per-route rate limits requiring Retry-After header handling on HTTP 429 responses.

Use this skill when sending Discord messages or DMs, managing roles, managing webhooks, or managing message reactions through Rube MCP.

Inputs: a Discord operation request (send message/DM, manage roles, manage webhooks, or manage reactions) with the relevant guild/channel/user/role snowflake IDs.

Outputs: sent or edited messages/DMs, created or assigned/removed roles, created or executed webhooks, and managed message reactions - resolved using correct snowflake IDs, permission bitfields, and pagination.

Rube MCP (https://rube.app/mcp), Composio's Discord/Discordbot toolkits (DISCORDBOT_CREATE_MESSAGE, DISCORDBOT_CREATE_DM, DISCORDBOT_CREATE_GUILD_ROLE, DISCORDBOT_CREATE_WEBHOOK, DISCORDBOT_EXECUTE_WEBHOOK), Discord OAuth/bot authentication.

Teams automating Discord server operations - messaging, role management, webhook integrations, and reaction management - via Rube MCP.