Omnicord

What OrygnsCode/Omnicord MCP server does

OrygnsCode/Omnicord MCP server connects an MCP client to Discord through a bot that you control. It covers routine server operations such as reading channel history, searching messages, resolving members and roles, sending messages, managing channels and roles, and checking bot health. The repository describes a larger tool catalog covering moderation, AutoMod, events, threads, forums, invites, onboarding, expressions, audit information, and live server events; the supplied tool list includes representative tools for these areas.

The server can also help create a community structure from a blueprint. Reference layouts provide starting points, while planning validates names, limits, dependencies, features, and bot permissions before changing anything. Execution is additive: matching channels and roles are reused, and existing entities are not deleted or modified by a build.

How it works

An AI client supplies the reasoning, and Omnicord performs Discord API operations through the configured bot. It does not contain its own language model or depend on a hosted cloud service. The default transport is stdio for desktop clients. Streamable HTTP is also available for self-hosting, with configurable binding, port, bearer authentication, and browser-origin restrictions.

Safety checks are part of the server. Delete operations first return a readable preview and a short-lived confirmation token; the action runs only when the same request is repeated with that token. The README also states that destructive moderation actions are preflighted against Discord hierarchy, owner, and self-protection rules. Rate-limit handling waits when Discord asks the client to slow down, and setup diagnostics report token, intent, guild, and membership problems with repair guidance.

Setup and configuration

OrygnsCode/Omnicord MCP server requires Node.js 20 or newer and a Discord account. The documented setup command is npx @orygn/omnicord init; the wizard accepts the bot token, verifies it, checks privileged intents, creates an invite, stores local configuration, and can add the MCP entry to detected client configuration files. Claude Desktop, Cursor, Windsurf, and project-level Claude Code are detected automatically. Other MCP clients receive a configuration snippet.

For a source checkout, the documented sequence is to clone the repository, run npm install, run npm run build, and start node dist/index.js. The bot token is provided through DISCORD_TOKEN, with optional defaults and behavior controlled by variables such as OMNICORD_GUILD, OMNICORD_TOOLS, OMNICORD_SAFE_MODE, and OMNICORD_GATEWAY. Multiple bots can be configured in bots.json; each can serve a different Discord server.

Tools and capabilities

The supplied catalog supports:

• Inspecting bot identity, gateway intents, guild count, rate limits, server structure, channels, roles, members, messages, and pins.
• Searching message history and members, resolving names to IDs, and reading detailed member profiles.
• Sending, forwarding, editing, pinning, and unpinning messages, including replies and embeds; other documented capabilities include DMs, webhooks, reactions, polls, and scheduled messages.
• Creating, updating, and deleting channels and roles, assigning roles, and setting voice-channel status.
• Planning and executing additive server builds from blueprints, with validation and resumable execution.
• Running setup checks before diagnosing a misconfigured bot.

Limitations and notes

The bot can act only where Discord grants it access and permissions. Message search covers channels the bot can read, and role-based member searches may report when a paging cap is reached. Discord does not allow the bot to edit messages sent by other users. Channel pinning requires the Pin Messages permission and is subject to Discord's 50-pin limit.

HTTP mode needs additional protection when exposed beyond localhost: the README requires OMNICORD_HTTP_TOKEN for non-loopback binding. The default safe mode previews destructive actions; disabling that behavior is available through configuration but is intended only for trusted automation. OrygnsCode/Omnicord MCP server is therefore best suited to deployments where the bot permissions, token storage, and confirmation flow can be controlled.