Discord MCP Integration

Weldable's Discord MCP integration connects your AI agents to your servers with 16 actions covering messages, channels, reactions, pins, and member management. Instead of building a custom bot, deploying it, and maintaining the infrastructure, you connect through OAuth and start giving instructions in plain English.

Discord servers are hubs for communities, open source projects, gaming groups, and developer teams. The common thread is that they all generate a high volume of messages that need monitoring, responding to, and organizing. An AI agent that can read, post, search, and manage channels turns a noisy server into a well-run operation.

Use cases

Release announcements

Your agent compiles changelog entries from GitHub (using Weldable's GitHub integration), formats them into a Discord embed with version number, key changes, and migration notes, then calls send message to post to your #announcements channel. Pin the message with pin message so it stays visible. Your community gets structured, consistent release notes without anyone copy-pasting between tools.

Community support triage

Your agent uses search messages to find unanswered questions in #help by filtering for messages without replies. It reads the content with get message, drafts a response using the Anthropic integration for reasoning, and posts the answer via send message. For questions that need human attention, it calls add reaction with a flag emoji so moderators can spot them during their next pass.

Open source project coordination

When a new contributor joins, your agent uses get guild member to check their roles, then sends a welcome message to #introductions with links to the contributing guide and open issues. For larger projects, it calls create channel to spin up feature-specific discussion spaces and uses list channels to audit which channels are active versus dormant.

Event management

Post event details to #events with send message using a rich embed (title, description, time, location fields). Pin the announcement with pin message so it stays at the top. Members react with emoji to RSVP, and your agent calls get pinned messages before the event to pull attendance from reaction counts. After the event, unpin message cleans up old announcements.

Developer team standups

Your agent calls read messages on #standup every morning to collect what each team member posted. It summarizes the updates using the Anthropic integration, then posts a consolidated digest to #standup-summary via send message. Managers get a single, scannable update instead of scrolling through individual posts.

How it works

Connect your Discord account through OAuth. Weldable handles the bot token, permissions, and token lifecycle so you never touch the Discord Developer Portal after initial setup. Your agent communicates in natural language, and Weldable maps your intent to the right API endpoint.

Actions can be chained together. Read messages from one channel, process the content, and post results to another. Combine Discord actions with other Weldable integrations to build workflows that span your entire toolchain.

Tips

Enable the MESSAGE_CONTENT intent. Discord requires this privileged intent to be turned on in the Developer Portal for your bot to read message content. Without it, read messages returns empty message bodies. This is a one-time setup step.

Respect embed character limits. Discord embeds have strict size constraints: 6,000 characters total across all fields, 4,096 for the description, 256 for the title, and 1,024 per field value. If your agent generates long content, break it across multiple embeds or use plain text messages instead.

Channels have a 50-pin limit. Once a channel hits 50 pinned messages, new pin message calls will fail. Build a cleanup step into any workflow that pins content. Use get pinned messages to audit and unpin message to remove stale pins before adding new ones.

Search filters narrow results fast. The search messages action supports filtering by author, channel, attachment type, and content keywords. Combining filters (like messages from a specific user that contain attachments) returns precise results without your agent processing the full message history.

Use channel categories for organization. When creating channels with create channel, you can assign a parent_id to place the new channel under an existing category. This keeps your server structure clean as your agent creates channels for new projects or events.