LABSCO SUMMARY
Reading message history is the permission that makes it two-way.
Sending alone would only need one permission; waiting for your answer is why the bot also reads history. That is the feature — an agent that can ask a question and act on the answer without you sitting at the terminal. Set the timeout to match how long you are willing to leave a job parked.
What it is
A Discord bridge for an assistant that needs your attention mid-task. It sends a notification with a mention, then waits for the reply and hands it back, so the run continues instead of stalling.
What you get
- Notifications sent to a channel with a mention, so they reach you rather than sit in a feed
- A reply-wait mode with a configurable timeout — the run pauses for your answer instead of guessing
- Configuration that can be changed while it is running
Requirements
Build from a checkout: clone the repo, bun install, copy discord-config.sample.json to discord-config.json, then bun run build. The config holds three values — the Discord bot token, the channel id and your user id. The client launches dist/index.js with node. Your bot needs three permissions in Discord: sending messages, reading message history, and viewing the channel.
Setup effort
Build from source — git clone git@github.com:s-yu-yu-yu/discord-notification-mcp.git
USE CASES
01
Being told when a long job finishes
Get a mention in Discord instead of checking a terminal you have walked away from.
02
Answering a question the agent hit mid-run
It waits on your reply up to the timeout, then continues with your answer.
03
Approving something risky from your phone
The agent asks in the channel and proceeds only once you have replied.
BEFORE YOU INSTALL
What to know first
Requires
- Bun, to install and build it (bun install, bun run build), and Node.js to run the built server
- A Discord bot token, the ID of the channel to post into and your Discord user ID, written into discord-config.json
- The bot needs permission to send messages, read message history and view the channel
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone git@github.com:s-yu-yu-yu/discord-notification-mcp.git
cd discord-notification-mcp
bun install
cp discord-config.sample.json discord-config.json
bun run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"discord-notification": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DISCORD_NOTIFICATION_MCP>/dist/index.js"
]
}
}
}