Crow

Crow is an MCP (Model Context Protocol) server built on the @modelcontextprotocol/sdk. It gives AI agents first-class access to Discord: discovery, messaging, channels, invites, emojis, stickers, moderation, and arbitrary REST calls, through a small set of typed, consent-aware tools.

Links

• Getting Started

• Tools

• Gateway

• Build And Release

• GitHub Releases

Related MCP server: discord-mcp-server

What is Crow?

Crow is a single-purpose MCP server that bridges an AI agent and a Discord bot account. Configure it once with a bot userId and token, connect it to any MCP client, and the agent can discover the guilds, members, and channels it has access to, then read and send messages, manage channels, apply consent-gated moderation, and fall back to raw Discord REST calls for edge cases.

Crow is deliberately small and convention-driven. Each capability is a self-contained tool module registered through a single registry, so adding a Discord feature is a matter of writing one file and registering it.

Capabilities

• Discovery: list guilds, members, channels, and bans so the agent can select its target.

• Overview: get_guild_overview gives a one-call orientation of a guild (basics + boost info, channels grouped by category, and roles).

• Notes: attach local, informational notes to users, roles, channels, messages, guilds, webhooks, and more, so context survives across agent sessions.

• Messaging: read (with embeds, components, and attachments), send, edit, delete, pin, and bulk-delete messages.

• Direct messages: list DM channels, send DMs, and read DM history with content, embeds, components, and attachments.

• Embeds: build rich embeds with Discord's limits enforced.

• Components: send messages with buttons, select menus, and Components V2 layout (containers, sections, text, media galleries, thumbnails, separators, files).

• Channels: full control: text/voice/forum settings, threads, forum posts, and permission overwrites.

• Guild config: set the guild name, description, and rules channel.

• Roles: create, modify, and delete roles; assign and remove them from members.

• Members: dedicated tools for timeouts, nicknames, and voice movement, plus role assignment.

• Self: read and modify the bot's own profile (username, avatar, banner, bio) and its per-guild member profile (nickname, guild avatar/banner/bio).

• Voice: read and modify stage-channel voice states (suppress, request-to-speak, and move between stage channels).

• Reactions: add, remove, and list message reactions.

• Audit: read the guild audit log.

• Community: manage the welcome screen, onboarding, and membership screening.

• Boost: read a guild's Server Boost level, boost count, and progress bar state.

• Webhooks: create, manage, and execute webhooks.

• Attachments: send files, images, and GIFs alongside messages.

• Invites: list, create, inspect, and delete guild and channel invites.

• Emojis: create, list, modify, and delete custom emojis.

• Stickers: create, list, modify, and delete guild stickers, plus sticker packs.

• Actions: register replies and modals for component interactions, and inspect the values users submit.

• Gateway: crow gateway daemon receives interactions live and dispatches registered actions.

• Moderation: kick and ban behind an explicit consent gate; list, unban, and count prunable members.

• Automod: create, list, modify, and delete auto-moderation rules.

• Scheduled events: create, list, modify, and delete guild scheduled events and list interested users.

• Polls: attach polls to messages, list voters, and end polls.

• Listening: wait_for_message blocks until a new message arrives in a channel.

• Guardrails: block tools by name, category, raw REST route, or whole guild.

• Raw REST: a generic Discord REST escape hatch for any endpoint the typed tools do not cover.

Destructive actions (kick_member, ban_member, delete_channel, delete_message, delete_webhook, delete_invite, delete_emoji, delete_sticker, delete_role, delete_automod_rule, delete_scheduled_event, bulk_delete_messages) require an explicit "confirm": true consent flag.

Every tool also declares MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) plus human-readable titles and per-field descriptions, so clients can present and permission the tools safely.

Tools

See docs/tools.md for the full reference, the selection pipeline, and the consent model.

Quick Start

Install with one command, which clones the repo, builds it, links the crow command onto your PATH, and drops you into the setup wizard:

curl -fsSL https://raw.githubusercontent.com/Hydr46605/Crow/main/install.sh | sh

Windows (PowerShell):

irm https://raw.githubusercontent.com/Hydr46605/Crow/main/install.ps1 | iex

Windows (cmd.exe):

curl -o install.bat https://raw.githubusercontent.com/Hydr46605/Crow/main/install.bat && install.bat

The wizard asks for your bot token, detects the bot user ID, verifies the token against Discord, and checks that the privileged intents Crow needs (GUILD_MEMBERS, MESSAGE_CONTENT) are enabled, prompting you to fix and re-check them if they are not.

Command line

Crow ships a single crow command:

Credentials live in ~/.crow/.env (owner-readable) and are loaded automatically, so an MCP client config is just:

{
  "mcpServers": {
    "crow": {
      "command": "crow"
    }
  }
}

Prefer inline credentials? You can still set CROW_BOT_TOKEN and CROW_BOT_USER_ID in the client's env block instead.

Build from source

git clone https://github.com/Hydr46605/Crow.git
cd Crow
npm install
npm run build
npm start

Compatibility

• Node.js >= 22 (CI runs against 22 and 24).

• ESM-only.

• Discord API v10 via discord.js.

• Distributed via GitHub (not npm); install with the scripts above.

• Maintenance: the repository is archived at v1.3.1 and receives no further updates.

License

MIT