GUIDE

How to Use a Discord MCP Server for TTRPG Campaign Management

Connect Claude or ChatGPT to Discord through a bot you control, then turn campaign memory into recaps, threads, polls, handouts, and fewer minutes spent copying text between tabs.

September 6, 2026 • 8 min read

← Back to the Blog Hub

The short version

Archivist Campaign MCP brings structured Archivist data into Claude, ChatGPT, and other AI clients. Discord MCP lets that client search and post inside Discord through a bot you control. Use either one by itself, or connect both when a workflow starts with campaign memory and ends in your server.

What Is a Discord MCP Server?

A Discord MCP server translates useful Discord actions into Model Context Protocol tools. Instead of asking an AI assistant to write a recap, copying it, finding the right channel, and formatting the post yourself, the assistant can use an approved tool to post it through a bot.

The protocol is the bridge. The Discord bot is still the identity inside your server. Discord permissions still decide which channels that bot can view and what it can do there. That distinction matters because an MCP connection should not quietly become a skeleton key to the server.

Discord MCP supports practical read and write workflows: search messages, inspect pins and threads, post replies, attach files, add reactions, start threads, and create polls. The hosted connection uses bot tokens only. User tokens and self-bots are rejected.

Campaign MCP vs. Discord MCP

TTRPG campaign management has two different kinds of context. One is the campaign record. The other is the conversation happening around it. Cramming both into a single vaguely named connector makes setup easier to misunderstand and permissions harder to reason about.

Connector	What it brings into your AI client	What it can change	You control access with
Archivist Campaign MCP	Structured Archivist data: sessions, characters, quests, journals, lore, and moments	Archivist campaign data when you grant write access	Archivist OAuth scopes and campaign permissions
Discord MCP	Discord messages, pins, threads, reactions, attachments, and server context	Discord posts, replies, threads, reactions, attachments, and polls. It does not write to Archivist.	Your bot's Discord permissions and your AI client's tool approvals

Use Campaign MCP by itself when the answer should stay in your AI client or update Archivist. Use Discord MCP by itself for Discord-native work. Connect both when the job starts with campaign memory and ends in your server.

Why Discord MCP Uses a Bot You Control

The separation keeps the connection under your control. Discord MCP does not turn the official Archivist bot into a general-purpose gateway, and it does not add your Discord messages to Archivist campaign memory. Archivist hosts the bridge that lets your AI client take the actions you approve through your bot.

Connection	Who controls it	What it is for	How access is limited
Official Archivist bot	Managed by Archivist	Recording, slash commands, and supported Archivist features	The permissions required for those Archivist features
Your Discord MCP bot	Created, named, installed, and selected by you	Discord actions requested by Claude, ChatGPT, or another MCP client	The Discord permissions you grant plus your client's tool settings and approvals

This gives you four visible control points:

Identity: the bot name and presence belong to the Discord application you created.
Reach: Discord permissions decide which channels the bot can view, read, and write.
Consent: Archivist OAuth records which bot the Discord MCP connection may use.
Tool approval: your AI client decides which Discord tools are enabled and when you must approve an action.

Message Content is a privileged Discord intent. Enable it if you want useful message search and reading. Without it, the bot can be installed correctly while read results contain almost no message body. That is secure in the way a locked filing cabinet with no files is secure, but not especially productive.

How to Connect Claude Desktop or ChatGPT to Discord with MCP

For Claude Desktop, download the latest Archivist Nexus for macOS or Windows and choose Discord MCP. For ChatGPT, add https://discord.myarchivist.ai/mcp in developer mode. Other compatible clients can use the same endpoint in their MCP settings.
Create an application in the Discord Developer Portal, add a Bot user, and copy its token.
Enable Message Content. Enable Server Members too if member search is part of your workflow.
Open Archivist Profile, choose Discord, select Add companion bot, and paste the token.
Choose Add to Discord and invite the bot to each server it should access. Existing companion bots may need to be invited again so message, thread, attachment, reaction, and poll permissions are added.
Return to your AI client, complete Discord MCP OAuth, and choose the companion bot on the consent screen.
Test one narrow action in a channel created for setup.

Prefer manual configuration? Add https://discord.myarchivist.ai/mcp to a compatible MCP client. Do not confuse it with https://mcp.myarchivist.ai/mcp, which is the Campaign MCP endpoint. The full distinction and troubleshooting steps live in the Discord MCP documentation.

Five TTRPG Campaign Management Workflows

1. Post a Session Recap

Ask Campaign MCP for the latest reviewed session, have Claude or ChatGPT write a player-safe recap, then use Discord MCP to post it in your recap channel. One prompt can preserve spoilers, use your preferred length, and keep the formatting consistent week to week.

2. Turn a Rules Debate into a Thread

Search recent Discord messages for the disputed rule, summarize the competing interpretations, and start a thread with the final table ruling. Next time the question comes up, your answer is searchable instead of buried between a meme and three scheduling messages.

3. Publish Handouts and Highlights

Pull a session handout, memorable quote, player spotlight, or hero award from Archivist and attach it to a Discord post. This is where structured campaign memory and Discord delivery work especially well together. Someone will still contest the hero award. Automation cannot fix taste.

4. Run the Scheduling Poll

Create a Discord poll with the dates your group is considering, post it in the scheduling channel, and keep the result beside the conversation. This does not require campaign data at all, so Discord MCP can handle it alone.

5. Build a Between-Session Digest

Summarize pinned notes, active campaign threads, unresolved rules questions, and recent attachments. Add open quests from Campaign MCP, then post one briefing before game night. It is less glamorous than generating an NPC portrait and substantially more likely to stop the GM from forgetting something important.

Discord MCP Permission Best Practices

Start with one test channel. Confirm search and posting behavior before widening access.
Use channel-level permissions. Give the bot access only where the workflow needs it.
Keep tokens out of chat and config screenshots. Store the bot token through Archivist's companion bot setup.
Review before broad posting. Ask for a draft first when the output includes spoilers, rulings, or player-sensitive information.
Separate Discord from campaign writes. Grant each connector only the access needed for the workflow.

If you also use the official Archivist bot for live recording, that setup continues to work. An Archivist companion bot is a Discord bot you create and connect to Archivist; it can serve both as an additional simultaneous voice connection and as the Discord MCP identity and permission boundary. Learn more in our D&D on Discord guide.

Common Discord MCP Setup Mistakes

The bot connects but message results are empty

Enable Message Content in the Discord Developer Portal, then reconnect. This is the most common cause.

The bot cannot post in a channel

Check View Channel, Send Messages, and any thread or attachment permissions needed in that specific channel.

An older companion bot can record but cannot use message tools

Choose Add to Discord again from Archivist so the server receives the expanded permission set.

The official Archivist bot is missing from OAuth

That is expected. Discord MCP only lists companion bots you create and connect.

Your AI assistant has Discord context but no campaign history

Connect Campaign MCP too. Discord MCP and Campaign MCP are separate by design.

Discord MCP FAQ

What is a Discord MCP server?

A Discord MCP server exposes Discord actions as Model Context Protocol tools so a compatible AI client can search, read, post, reply, create threads, react, or run polls through an authorized Discord bot.

Can Claude or ChatGPT connect to Discord with MCP?

Yes. Archivist Nexus can configure Claude Desktop with Discord MCP. ChatGPT and other compatible clients can connect to the hosted endpoint directly. The server uses OAuth and an Archivist companion bot that you create, install, and select during consent.

What is the difference between Discord MCP and a Discord bot?

The Discord bot is the identity and permission boundary inside Discord. Discord MCP is the tool layer that lets an AI client use that bot for approved read and write actions.

Why does Discord MCP need Message Content permission?

Discord requires the privileged Message Content intent for useful message bodies in read and search results. Without it, the bot can connect but message content is mostly unavailable.

How does Discord MCP help with TTRPG campaign management?

It can find table discussions, organize rules questions into threads, publish session recaps and handouts, post campaign updates, collect poll responses, and pair with campaign-memory tools to keep Discord aligned with the game record.

Connect Discord MCP to Your AI Client

Bring the bot, choose its permissions, and let Claude or ChatGPT handle the repetitive parts of keeping a campaign server useful.

Explore Discord MCP Download Nexus