OrygnsCode/Omnicord

Discord server management MCP for AI agents.
Omnicord is an MCP server that gives your AI assistant full operational
control of a Discord server. Day to day chat, moderation, administration,
and at the top end: building out an entire community server from a one
paragraph brief.
You describe what you want. Your AI decides how to do it. Omnicord makes
sure it happens correctly, and that nothing destructive happens without
your say so.
How it works
Your AI client (Claude Desktop, Cursor, Windsurf, Claude Code, or any
other MCP client) is the brain. Omnicord is the hands: it talks to
Discord through your own bot, enforces Discord's rules before they bite,
queues politely behind rate limits, and gates every destructive action
behind a preview you confirm. There is no LLM inside Omnicord and no
cloud service behind it. Your bot token stays in a file on your machine.
Quick start
You need Node 20 or newer and a Discord account. One command:
Or from source:
Prefer to watch? Here is the full setup, start to finish:
This walkthrough is a little dated now, but the core steps still apply. A
fuller, updated walkthrough is planned.
The wizard goes from a bare Discord application to a working setup in
about a minute. It takes the bot token with input hidden, verifies it
live against Discord, checks the privileged intent toggles and waits
while you fix any that are off, generates an invite link at the
permission level you pick, saves the token locally (a gitignored .env
for a source checkout, or .omnicord/.env in your user folder for an
npx or global install), and writes the omnicord entry into your AI
client's config (backing the file up first). Claude Desktop (including the Microsoft Store build), Cursor,
Windsurf, and project level Claude Code are detected automatically, even
before you have set up MCP in them; anything else gets a snippet to
paste. It only adds the omnicord entry and never overwrites the rest of
the file.
Then fully restart your AI client and ask it:
> run a setup check on my Discord bot
Eight checks, plain English results, and the exact fix for anything that
is wrong.
What it can do
| Area | Examples |
|---|---|
| Server building | Plan and execute a full server build from a brief: roles, categories, channels, permissions, in one additive operation. Save, diff, and rebuild layouts as blueprints. |
| Messaging | Send, edit, pin, forward, react, polls, scheduled messages, DMs, webhooks, and rich Components V2 layouts for rules and welcome panels. |
| Reading | Channel history, full-text message search, members, roles, permissions, audit log. |
| Moderation | Timeouts, kicks, bans, bulk actions, and prune, all preview first, plus raid lockdown to pause invites and DMs. |
| AutoMod | Discord's server side filters: keyword rules, Discord maintained preset lists (slurs, profanity), member profile checks, spam and mention flood limits. |
| Real time | Subscribe to live server events and ask "what did I miss?" |
| Structure | Channels, categories, permission overwrites, reordering, cloning, voice channel status. |
| Community | Events (one-off or recurring), stages, threads, forums, invites, welcome screen, onboarding. |
| Expression | Emojis, stickers, soundboard sounds. |
| Diagnostics | Setup check, bot info, rate limit status, permission explainers. |
The full contract for every tool is in the
tool catalog.
The safety model
Destructive operations (deleting, banning, kicking, timeouts, bulk
actions) never execute on the first call. They return a human readable
preview and a confirmation token bound to that exact action; repeating
the call with the token executes it. Tokens are single use and expire
after two minutes. Moderation additionally preflights Discord's