Discord MCPmonday.com

Create monday.com items from Discord messages

A Discord MCP + monday.com agent flow

A community runs its support and feedback in a Discord server: a #bugs channel, a #feature-requests channel, the usual. Good reports get a thumbs-up and then sink under the next hundred messages, and the team that works out of monday.com never sees them. This recipe pulls the signal out: your agent searches a Discord channel for messages that read like reports and creates an item on the monday board the team actually tracks. It calls discord_search_messages scoped to the channel and a keyword or phrase, reads back the matching messages, and calls create_item with the message text, the author, and a link to the message, mapping column values for status or source if your board has them. Discord answers when the agent asks, so it runs on a cadence, and only messages that match become board items.

The flow

Discord MCPdiscord_search_messages

Search messages in a server.

monday.comcreate_item

Creates a new item in a board, optionally with column values.

Step by step

  1. Pick the channel and what counts as a report

    Point the agent at the Discord server and channel, like #bugs, and give it a query that isolates real reports from chatter. Map it to one monday board so items don't scatter.

  2. Search the channel

    The agent calls discord_search_messages with your query and gets back the matching messages, each with its author, timestamp, and content. It can pull surrounding context with discord_read_messages if a report spans replies.

  3. Create the board item

    It calls create_item with the message as the item name or in a text column, and sets column values you map: a status of 'New', a source column noting Discord, and a link column pointing at the original message.

  4. Track what's already on the board

    Store each Discord message ID against the monday item it produced. Next run, the agent skips messages that already have an item so re-running doesn't duplicate the board.

Tell your agent

Every hour, search the #bugs channel in the Acme Discord for messages containing 'crash' or 'broken'. For each one not already on the board, create an item on the Community Bugs board with the message text as the name, the status column set to New, a Source column set to Discord, and a link to the message. Don't recreate items for messages you've already filed.

Setup

This flow needs both servers connected to your agent. Follow each install guide:

Worth knowing

  • create_item sets column values by column ID and a typed JSON value, not by the labels you see in the UI. Pull the board's columns once with get_board_schema and map each field to its ID and the value shape monday expects.
  • discord_search_messages needs the bot to be in the server and able to read that channel. Confirm the bot has the View Channel and Read Message History permissions, or the search comes back empty even when the channel is busy.
  • Discord search matches on content, so noisy keywords pull in jokes and false positives. Tighten the query and consider requiring the message to be in a dedicated reports channel rather than searching server-wide.

Questions

Can it react back in Discord once an item is created?
Not in this recipe; it's create-only into monday. You could add a step that calls discord_add_reaction on the source message so community members see their report was logged, keyed on the message ID you stored.
Does it pick up reports the instant they're posted?
No. The Discord server answers the agent's search, it doesn't push new messages. The board lags by your polling interval, so tighten the cadence if a channel moves fast.
How does it keep the board from filling with duplicates?
It records the Discord message ID alongside each monday item. On every run it searches current messages, removes the ones already mapped, and only creates items for the rest.