An MCP server enabling async communication between AI agents and users via Discord - perfect for long-running tasks requiring remote interaction
An MCP server enabling async communication between AI agents and users via Discord - perfect for long-running tasks requiring remote interaction. The mcp discord agent comm mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
An MCP (Model Context Protocol) server that enables async communication between AI agents and users via Discord. Perfect for long-running AI tasks where you need remote interaction capabilities.
Everything the assistant can do here goes through one of these:
Notifications — Direct message to channel (when expect_reply is false or omitted)Timeouts — Users must reply to messages (not just type in channel) or click reactionsdiscord_message — Send a message to Discord, optionally waiting for a responsemcp-discord-agent-comm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: DISCORD_BOT_TOKEN, DISCORD_CHANNEL_ID. 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.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Discord Agent Comm's toolset — Notifications, Timeouts, discord_message — is a fair guide to whether it matches your workflow. It is maintained by EugenEistrach; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Notifications | Direct message to channel (when expect_reply is false or omitted) |
| Timeouts | Users must reply to messages (not just type in channel) or click reactions |
| discord_message | Send a message to Discord, optionally waiting for a response. |
{
"mcpServers": {
"discord-agent-comm": {
"command": "npx",
"args": ["mcp-discord-agent-comm"],
"env": {
"DISCORD_BOT_TOKEN": "your-bot-token-here",
"DISCORD_CHANNEL_ID": "your-channel-id-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DISCORD_BOT_TOKEN | Credential the server authenticates with. | Yes |
| DISCORD_CHANNEL_ID | Configuration value read at startup. | 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.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.