Discord MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| discordToken | No | Your Discord bot token (alternative camelCase environment name supported by some clients) | |
| DISCORD_TOKEN | No | Your Discord bot token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversB | List the Discord servers the bot is currently connected to. |
| get_server_infoB | Retrieve detailed information about a Discord server. |
| get_channelsB | List channels for a Discord server grouped by category. |
| list_rolesB | List all roles defined in the Discord server. |
| list_membersC | List members of a Discord server. |
| get_user_infoB | Fetch information about a specific Discord user. |
| send_messageC | Send a message to a Discord text channel or thread. |
| read_messagesC | Read recent messages from a channel. |
| add_reactionC | Add a reaction to a specific message. |
| add_multiple_reactionsC | Add multiple reactions to a message. |
| remove_reactionC | Remove the bot's reaction from a message. |
| pin_messageC | Pin a message in a text channel. |
| unpin_messageC | Unpin a message in a text channel. |
| bulk_delete_messagesC | Delete multiple recent messages from a channel. |
| create_text_channelC | Create a new text channel in the specified server. |
| create_voice_channelC | Create a new voice channel in the specified server. |
| create_stage_channelC | Create a new stage channel for events and announcements. |
| create_categoryC | Create a new channel category. |
| update_channelC | Update channel settings such as name, topic, and category. |
| delete_channelC | Delete a Discord channel. |
| create_inviteC | Create an invite link for a channel. |
| list_invitesB | List active invites for a server. |
| create_roleC | Create a new role in the specified server. |
| edit_roleC | Update the configuration of an existing role. |
| delete_roleC | Delete a role from the server. |
| add_roleC | Add a role to a Discord user. |
| remove_roleC | Remove a role from a Discord user. |
| kick_memberC | Kick a member from the server. |
| ban_memberC | Ban a user from the server. |
| unban_memberC | Remove a ban for a user. |
| list_bansB | List banned users for the server. |
| timeout_memberC | Apply or clear a communication timeout for a member. |
| moderate_messageB | Moderate a message by deleting it and optionally timing out the author. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Each tool has a clearly distinct purpose targeting specific Discord resources and actions, such as add_reaction vs. remove_reaction or create_text_channel vs. delete_channel. There is no significant overlap that would cause confusion in tool selection, as descriptions precisely define the scope of each operation.
Tool names follow a consistent verb_noun pattern throughout, such as create_role, list_members, and update_channel. All tools use snake_case with clear, descriptive verbs, making the naming scheme predictable and easy to understand across the entire set.
With 33 tools, the count is slightly high but reasonable for a comprehensive Discord server management system, covering channels, roles, members, messages, and moderation. It feels slightly heavy but not excessive, as each tool serves a specific function in the domain.
The tool set provides complete CRUD and lifecycle coverage for Discord server management, including creation, retrieval, updating, and deletion of channels, roles, and messages, along with moderation actions like ban, kick, and timeout. No obvious gaps exist for the intended purpose, ensuring agents can handle typical workflows without dead ends.