discord-automation
Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.
Best use case
discord-automation is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.
Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "discord-automation" skill to help with this workflow task. Context: Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/discord-automation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How discord-automation Compares
| Feature / Agent | discord-automation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Discord Automation via Rube MCP Automate Discord operations through Composio's Discord/Discordbot toolkits via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Discord connection via `RUBE_MANAGE_CONNECTIONS` with toolkits `discord` and `discordbot` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `discordbot` (bot operations) or `discord` (user operations) 3. If connection is not ACTIVE, follow the returned auth link to complete Discord auth 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Send Messages **When to use**: User wants to send messages to channels or DMs **Tool sequence**: 1. `DISCORD_LIST_MY_GUILDS` - List guilds the bot belongs to [Prerequisite] 2. `DISCORDBOT_LIST_GUILD_CHANNELS` - List channels in a guild [Prerequisite] 3. `DISCORDBOT_CREATE_MESSAGE` - Send a message [Required] 4. `DISCORDBOT_UPDATE_MESSAGE` - Edit a sent message [Optional] **Key parameters**: - `channel_id`: Channel snowflake ID - `content`: Message text (max 2000 characters) - `embeds`: Array of embed objects for rich content - `guild_id`: Guild ID for channel listing **Pitfalls**: - Bot must have SEND_MESSAGES permission in the channel - High-frequency sends can hit per-route rate limits; respect Retry-After headers - Only messages sent by the same bot can be edited ### 2. Send Direct Messages **When to use**: User wants to DM a Discord user **Tool sequence**: 1. `DISCORDBOT_CREATE_DM` - Create or get DM channel [Required] 2. `DISCORDBOT_CREATE_MESSAGE` - Send message to DM channel [Required] **Key parameters**: - `recipient_id`: User snowflake ID for DM - `channel_id`: DM channel ID from CREATE_DM **Pitfalls**: - Cannot DM users who have DMs disabled or have blocked the bot - CREATE_DM returns existing channel if one already exists ### 3. Manage Roles **When to use**: User wants to create, assign, or remove roles **Tool sequence**: 1. `DISCORDBOT_CREATE_GUILD_ROLE` - Create a new role [Optional] 2. `DISCORDBOT_ADD_GUILD_MEMBER_ROLE` - Assign role to member [Optional] 3. `DISCORDBOT_DELETE_GUILD_ROLE` - Delete a role [Optional] 4. `DISCORDBOT_GET_GUILD_MEMBER` - Get member details [Optional] 5. `DISCORDBOT_UPDATE_GUILD_MEMBER` - Update member (roles, nick, etc.) [Optional] **Key parameters**: - `guild_id`: Guild snowflake ID - `user_id`: User snowflake ID - `role_id`: Role snowflake ID - `name`: Role name - `permissions`: Bitwise permission value - `color`: RGB color integer **Pitfalls**: - Role assignment requires MANAGE_ROLES permission - Target role must be lower in hierarchy than bot's highest role - DELETE permanently removes the role from all members ### 4. Manage Webhooks **When to use**: User wants to create or use webhooks for external integrations **Tool sequence**: 1. `DISCORDBOT_GET_GUILD_WEBHOOKS` / `DISCORDBOT_LIST_CHANNEL_WEBHOOKS` - List webhooks [Optional] 2. `DISCORDBOT_CREATE_WEBHOOK` - Create a new webhook [Optional] 3. `DISCORDBOT_EXECUTE_WEBHOOK` - Send message via webhook [Optional] 4. `DISCORDBOT_UPDATE_WEBHOOK` - Update webhook settings [Optional] **Key parameters**: - `webhook_id`: Webhook ID - `webhook_token`: Webhook secret token - `channel_id`: Channel for webhook creation - `name`: Webhook name - `content`/`embeds`: Message content for execution **Pitfalls**: - Webhook tokens are secrets; handle securely - Webhooks can post with custom username and avatar per message - MANAGE_WEBHOOKS permission required for creation ### 5. Manage Reactions **When to use**: User wants to view or manage message reactions **Tool sequence**: 1. `DISCORDBOT_LIST_MESSAGE_REACTIONS_BY_EMOJI` - List users who reacted [Optional] 2. `DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS` - Remove all reactions [Optional] 3. `DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS_BY_EMOJI` - Remove specific emoji reactions [Optional] 4. `DISCORDBOT_DELETE_USER_MESSAGE_REACTION` - Remove specific user's reaction [Optional] **Key parameters**: - `channel_id`: Channel ID - `message_id`: Message snowflake ID - `emoji_name`: URL-encoded emoji or `name:id` for custom emojis - `user_id`: User ID for specific reaction removal **Pitfalls**: - Unicode emojis must be URL-encoded (e.g., '%F0%9F%91%8D' for thumbs up) - Custom emojis use `name:id` format - DELETE_ALL requires MANAGE_MESSAGES permission ## Common Patterns ### Snowflake IDs Discord uses snowflake IDs (64-bit integers as strings) for all entities: - Guilds, channels, users, roles, messages, webhooks ### Permission Bitfields Permissions are combined using bitwise OR: - SEND_MESSAGES = 0x800 - MANAGE_ROLES = 0x10000000 - MANAGE_MESSAGES = 0x2000 - ADMINISTRATOR = 0x8 ### Pagination - Most list endpoints support `limit`, `before`, `after` parameters - Messages: max 100 per request - Reactions: max 100 per request, use `after` for pagination ## Known Pitfalls **Bot vs User Tokens**: - `discordbot` toolkit uses bot tokens; `discord` uses user OAuth - Bot operations are preferred for automation **Rate Limits**: - Discord enforces per-route rate limits - Respect `Retry-After` headers on 429 responses ## Quick Reference | Task | Tool Slug | Key Params | |------|-----------|------------| | List guilds | DISCORD_LIST_MY_GUILDS | (none) | | List channels | DISCORDBOT_LIST_GUILD_CHANNELS | guild_id | | Send message | DISCORDBOT_CREATE_MESSAGE | channel_id, content | | Edit message | DISCORDBOT_UPDATE_MESSAGE | channel_id, message_id | | Get messages | DISCORDBOT_LIST_MESSAGES | channel_id, limit | | Create DM | DISCORDBOT_CREATE_DM | recipient_id | | Create role | DISCORDBOT_CREATE_GUILD_ROLE | guild_id, name | | Assign role | DISCORDBOT_ADD_GUILD_MEMBER_ROLE | guild_id, user_id, role_id | | Delete role | DISCORDBOT_DELETE_GUILD_ROLE | guild_id, role_id | | Get member | DISCORDBOT_GET_GUILD_MEMBER | guild_id, user_id | | Update member | DISCORDBOT_UPDATE_GUILD_MEMBER | guild_id, user_id | | Get guild | DISCORDBOT_GET_GUILD | guild_id | | Create webhook | DISCORDBOT_CREATE_WEBHOOK | channel_id, name | | Execute webhook | DISCORDBOT_EXECUTE_WEBHOOK | webhook_id, webhook_token | | List webhooks | DISCORDBOT_GET_GUILD_WEBHOOKS | guild_id | | Get reactions | DISCORDBOT_LIST_MESSAGE_REACTIONS_BY_EMOJI | channel_id, message_id, emoji_name | | Clear reactions | DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS | channel_id, message_id | | Test auth | DISCORDBOT_TEST_AUTH | (none) | | Get channel | DISCORDBOT_GET_CHANNEL | channel_id |
Related Skills
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
wrike-automation
Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.
workflow-automation
Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility
whatsapp-automation
Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas.
webflow-automation
Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.
vercel-automation
Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.
trello-automation
Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.
todoist-automation
Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.
tiktok-automation
Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas.
telegram-automation
Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.