Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Discord MCP server exists for a simple reason — assistants are far more useful when they can act on Discord directly instead of describing what you should do. Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Default MCP endpoint URL (HTTP profile): http://localhost:8085/mcp
Installation goes through your MCP client rather than a global install: point it at saseq/discord-mcp on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Discord is connected, these are the calls the assistant has available:
Notes — 🖥 Claude Desktop Connection You will need 6 environment variables: DISCORD_TOKEN, DISCORD_GUILD_ID, SPRING_PROFILES_ACTIVE, YOUR_DISCORD_BOT_TOKEN, OPTIONAL_DEFAULT_SERVER_ID, PUBLIC_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Discord's toolset — Notes — is a fair guide to whether it matches your workflow. It is maintained by SaseQ; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Notes | <details> <summary style="font-size: 1.35em; font-weight: bold;"> 🖥 Claude Desktop Connection </summary> |
{
"mcpServers": {
"discord-2": {
"command": "docker",
"args": ["run", "-i", "--rm", "saseq/discord-mcp"],
"env": {
"DISCORD_TOKEN": "your-value",
"DISCORD_GUILD_ID": "your-value",
"SPRING_PROFILES_ACTIVE": "your-value",
"YOUR_DISCORD_BOT_TOKEN": "your-value",
"OPTIONAL_DEFAULT_SERVER_ID": "your-value",
"PUBLIC_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DISCORD_TOKEN | Credential the server authenticates with. | Yes |
| DISCORD_GUILD_ID | Configuration value read at startup. | Optional |
| SPRING_PROFILES_ACTIVE | Configuration value read at startup. | Optional |
| YOUR_DISCORD_BOT_TOKEN | Credential the server authenticates with. | Yes |
| OPTIONAL_DEFAULT_SERVER_ID | Configuration value read at startup. | Optional |
| PUBLIC_HOST | Endpoint or connection string the server talks to. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.
Enables AI assistants to interact with the Discord platform via a Model Context Protocol (MCP) server.