Crow
Provides tools for interacting with Discord servers, enabling AI agents to discover guilds, members, and channels, read and send messages, manage channels, roles, members, and moderation, handle embeds, components, reactions, webhooks, invites, emojis, stickers, and more via a Discord bot account.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CrowWhat's the latest message in #announcements?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
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_overviewgives 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, 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 and select menus.
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: edit nicknames, voice state, and timeouts.
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 gatewaydaemon receives interactions live and dispatches registered actions.Moderation: kick and ban behind an explicit consent gate; list and unban.
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,
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
Module | Tools |
Health |
|
Discovery |
|
Overview |
|
Messaging |
|
Direct messages |
|
Embeds |
|
Channels & threads |
|
Guild config |
|
Roles |
|
Members |
|
Self |
|
Voice |
|
Reactions |
|
Audit |
|
Community |
|
Boost |
|
Webhooks |
|
Invites |
|
Emojis |
|
Stickers |
|
Actions |
|
Notes |
|
Moderation |
|
Raw |
|
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 | shWindows (PowerShell):
irm https://raw.githubusercontent.com/Hydr46605/Crow/main/install.ps1 | iexWindows (cmd.exe):
curl -o install.bat https://raw.githubusercontent.com/Hydr46605/Crow/main/install.bat && install.batThe 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:
Command | What it does |
| Run the MCP server over stdio. |
| Interactive setup wizard (token → user ID → intent check → save). |
| Check the bot token and privileged intents. |
| Run the always-on interaction gateway daemon. |
| Print the version. |
| Show help. |
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 startCompatibility
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.
License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Discord-based AI agent-user communication. Enables AI agents to communicate with users through Discord instead of IDE chat interfaces.59MIT
- Alicense-qualityDmaintenanceLets any MCP-compatible AI client interact with Discord — send messages, manage channels, create webhooks, assign roles, and more.11MIT
- Alicense-qualityDmaintenanceAn MCP server that enables AI agents to communicate with humans through Discord. Agents can send messages, create threads, wait for replies, and manage conversations across any MCP client.10ISC
- Alicense-qualityCmaintenanceA Discord MCP server that gives AI agents full control of a Discord bot — messages, channels, roles, threads, forums, events, webhooks, reactions, moderation, image generation, and real-time voice.586MIT
Related MCP Connectors
An MCP server that integrates with Discord to provide AI-powered features.
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hydr46605/Crow'
If you have feedback or need assistance with the MCP directory API, please join our Discord server