Connect Discord to Claude Code

Let Claude post, reply, and manage threads in Discord. From the terminal, inside the sessions where you already work.

How do you connect Discord to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Discord, you add a Discord MCP server: a small hosted service that exposes Discord's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Discord account. No API keys pasted into config files.

claude mcp add --transport http discord https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Discord once connected?

Full read-write Discord access lets Claude post a message in the right channel, reply inside a thread, react to or pin a message, and manage roles or threads once you approve. The triage and responses that used to mean switching apps happen where the conversation already lives.

Post a message to a specific channel after you approve it
Reply inside an existing thread, keeping the discussion in context
Start or archive a thread to organize a busy channel
Add a reaction or pin a message to flag it for the team
Assign or remove a role when someone is onboarded
Find messages matching a query and propose batched responses

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Discord access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Discord API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Discord changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Discord connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Discord connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Discord account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Discord's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Discord?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Discord account it signs in with. Revoking access is one click in Discord.

More on the Discord connector

Discord connector for claude.ai Slack + Claude Code Microsoft Teams + Claude Code Front + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us