MCP connectorsDiscord

Discord MCP: connect Discord to Claude and ChatGPT

Ask Claude or ChatGPT what your community asked about the new release, what was agreed in the server you share with a partner or which bug reports came in overnight. The answer comes from Discord, with a link to every message it relies on.

With Deployed OS everyone connects with their own Discord account. Your company’s bot does the reading, but only of what that person can see in Discord, and nothing is ever posted.

4 read actions · read-only · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Discord in Claude and ChatGPT

Community

What the community said this week

Read #general, #feedback and the busiest threads and get the themes: what people like, what they ask for and what broke. With links to the messages.

Customer support

Bug reports, sorted

Go through #bug-reports since Friday, group the reports by issue and see which came with a screenshot or log file. Ready for the Monday triage.

Partnerships

Servers you share with partners and customers

Catch up on the channel you share with a partner or a customer before the call: open questions, what was promised and by whom.

Engineering

Your internal server, searchable

If your team works in Discord, find the message where the release date or the API change was settled. Search covers the latest 500 messages in a channel.

Examples

Ask it like this

“What were the main questions in #help this week? Group them and link one example of each.”
“Summarise the feedback on version 2.4 in #feedback since the release.”
“Which threads in the Acme partner channel are still active, and what is each one about?”
“Search #bug-reports for crash and list who reported it and when.”
“What did Lina say about the API rate limits in #dev?”
“List the channels in our community server with their topics, so I can see where support questions go.”

The connector

What the Discord MCP connector does today

Readsdiscord_list_servers
Lists the servers you are in that the company’s bot can read, with name, member count and link.
Readsdiscord_list_channels
Lists the channels and active threads in a server that you can see, with category, topic and link. Hidden channels are left out.
Readsdiscord_read_channel
Reads the latest messages in a channel or thread you can see, with authors, replies, attachments by name, reactions and links, and further back when you ask.
Readsdiscord_search_messages
Finds recent messages in one channel or thread by words in the text, the author or attachment names. Scans the latest 500 messages at most.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Read-only: The connector lists servers and channels and reads messages, replies, reactions and attachment names in the channels and threads you can see. It cannot post, react, pin or change anything, and nobody is notified.
What you can see, nothing more: Everyone connects their own Discord account. The company’s bot reads for them, but every call checks that person’s roles and the channel permissions, so a channel hidden from you in Discord is hidden here too.
You choose who gets it: Admins decide which groups at the company can use the Discord connector. The bot reads only servers it has been added to, and a server without the bot cannot be read at all.
Every call logged: Who asked, which connector, when. Deployed OS shows reads per connector and per person, and the log can be exported.

Setup

Set up the Discord connector in three steps

An admin creates an app in the Discord Developer Portal, turns on Public Client and the Message Content Intent, and copies the Application ID and the bot token. Your company owns the app, not us.

The admin adds the bot to each server the AI should read, with View Channels and Read Message History only, then pastes the Application ID and bot token into Deployed OS and chooses which groups get Discord.

Each person connects their own Discord account. From then on they just ask.

Questions

Discord MCP: common questions

Not from Discord itself, as of October 2026. There are community-built servers, and most run on a single bot token, so the bot decides what the AI can read for everyone. Deployed OS gives the whole company one Discord connection where each person reads only what they can see in Discord, with access per group and a log of every call.

No. The connector only reads. Nothing is posted, reacted to, pinned or changed, and nobody is notified. If you want it to post, for example announcements, we can extend it for you.

Discord lets apps read channels through a bot. Your company’s bot does the reading, and each person’s own login shows who they are and which roles they have. The connector combines the two, so nobody reads more through the AI than they can in Discord.

Yes, to each server the AI should read, with View Channels and Read Message History. The bot sees a channel only where its role may, and people see only what they can see themselves. Search covers the latest 500 messages of one channel at a time.

Yes. Deployed OS is your company’s own MCP, so the same Discord connection works in Claude, ChatGPT and Copilot. People keep the assistant they prefer.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors

Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

You’ll hear from Poyan Karimi

Co-founder · Deployed AI