Omnicord MCP Server

Your AI runs your Discord server: chat, moderation, admin, even building it all from one brief.

Remote serverstreamable-httpGo

What is the Omnicord MCP server?

Omnicord MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Your AI runs your Discord server: chat, moderation, admin, even building it all from one brief.

What you get

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.

What the assistant can call

Once Omnicord is connected, these are the calls the assistant has available:

  • Area — Examples
  • Messaging — Send, edit, pin, forward, react, polls, scheduled messages, DMs, webhooks
  • 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
  • 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
  • Variable — What it does
  • DISCORD_TOKEN — The bot token. Required for anything real; the server boots without it and the diagnostics explain what to fix
  • OMNICORD_GUILD — Optional default server ID so tools can omit the guild parameter

Configuration and credentials

You will need 3 environment variables: DISCORD_TOKEN, OMNICORD_HTTP_TOKEN, OMNICORD_HTTP_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.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

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. Omnicord's toolset — Area, Messaging, Reading and 11 more — is a fair guide to whether it matches your workflow. It is maintained by OrygnsCode; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Omnicord's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Omnicord.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the omnicord mcp server does with a few real requests.

Available tools

ToolWhat it does
AreaExamples
MessagingSend, edit, pin, forward, react, polls, scheduled messages, DMs, webhooks.
ReadingChannel history, full-text message search, members, roles, permissions, audit log.
ModerationTimeouts, kicks, bans, bulk actions, and prune, all preview first, plus raid lockdown to pause invites and DMs.
AutoModDiscord's server side filters: keyword rules, Discord maintained preset lists (slurs, profanity), member profile checks, spam and mention flood limits.
StructureChannels, categories, permission overwrites, reordering, cloning, voice channel status.
CommunityEvents (one-off or recurring), stages, threads, forums, invites, welcome screen, onboarding.
ExpressionEmojis, stickers, soundboard sounds.
DiagnosticsSetup check, bot info, rate limit status, permission explainers.
VariableWhat it does
DISCORD_TOKENThe bot token. Required for anything real; the server boots without it and the diagnostics explain what to fix.
OMNICORD_GUILDOptional default server ID so tools can omit the guild parameter.
OMNICORD_SAFE_MODEDefault on. Destructive tools preview first and require a confirm token; set to false only for trusted automation.
OMNICORD_GATEWAYDefault on when a token is set: the bot shows as online and real time event subscriptions work. Set to off for REST only operation.

How to install the Omnicord MCP server

{
  "mcpServers": {
    "omnicord": {
      "command": "node",
      "args": ["/absolute/path/to/dist/index.js"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DISCORD_TOKENCredential the server authenticates with.Yes
OMNICORD_HTTP_TOKENCredential the server authenticates with.Yes
OMNICORD_HTTP_HOSTEndpoint or connection string the server talks to.Optional

Example prompts to try

  • Use Omnicord to Area.
  • Use Omnicord to Messaging.
  • Use Omnicord to Reading.

Frequently asked questions

It connects Omnicord to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Area, Messaging, Reading, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Omnicord directly.