Labsco
MCP SERVER

Discord Notification MCP Server

by s-yu-yu-yu

Let a long-running task ping you on Discord — and wait for your reply.

Notifications & Alerting to Humans
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.