Find the useful bit
Search messages, pins, threads, reactions, and attachments available to your bot. No archaeology degree required.
Discord MCP
Give Claude Desktop, ChatGPT, and other MCP clients a consent-first way to search, post, reply, thread, react, and poll in Discord through your own Archivist companion bot.
Not the official Archivist bot. Not a user token. Not a mysterious little creature living in your DMs.
Search messages, pins, threads, reactions, and attachments available to your bot. No archaeology degree required.
Send or edit messages, reply, start threads, react, attach files, and create polls through your bot.
Look up channels, members, roles, invites, scheduled events, emojis, and other server context your bot can access.
Use Archivist Campaign MCP for the campaign record, then Discord MCP to post a recap, quote, handout, or deeply unfortunate hero award.
The important distinction
Works with structured campaign data inside Archivist: sessions, characters, quests, journals, lore, moments, and campaign updates.
Campaign MCP details →Brings Discord channels and messages into your AI client, then posts and organizes through the bot you select. It does not write to Archivist campaign memory.
https://discord.myarchivist.ai/mcpAn Archivist companion bot is a Discord bot you create and connect to Archivist. It can record an additional simultaneous live session and serve as the Discord identity and permission boundary for the hosted Discord MCP.
You control the connection, not Archivist. Discord MCP only acts when your AI client requests an enabled tool. It does not continuously monitor Discord or add Discord messages to Archivist campaign memory.
You make the Discord application, hold its token, and register it in your Archivist account.
Discord channel permissions decide where the bot can see and act. Private stays private unless you invite the bot in.
The consent screen asks which companion bot Discord MCP may use. The official Archivist bot does not appear.
Your AI client controls which Discord tools are enabled and when an action needs your approval.
Setup
No. It uses a Discord bot token. User tokens and self-bots are rejected.
No. It follows the selected bot's Discord permissions. If the bot cannot view a channel, Discord MCP cannot view it either.
That separation keeps the connection under your control. Discord MCP only works with a companion bot you create, install, configure, and choose during consent. The official bot keeps its existing Archivist duties.
Not for Discord-only work. Add Campaign MCP when you want Claude, ChatGPT, or another AI client to use structured session history, characters, quests, journals, or other Archivist campaign data in the same workflow.
Yes. ChatGPT users and advanced users of other compatible clients can add https://discord.myarchivist.ai/mcp directly and complete OAuth in Archivist. Nexus is the guided Claude Desktop path.
Use Nexus with Claude Desktop or connect from ChatGPT, then let your AI client handle the Discord busywork.