discord-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discord_list_guildsA | List all Discord servers (guilds) the user is a member of. |
| discord_list_channelsB | List text channels in a guild. |
| discord_get_messagesA | Get messages from a channel. Uses local cache if daemon is running, Discord API otherwise. |
| discord_get_dmsA | List the user's open DM conversations. |
| discord_resolve_dm_userA | Resolve a username or display name to a DM channel ID. Use this before discord_get_messages when you know who to DM but not the channel ID. |
| discord_send_messageA | Send a message to a channel or user (DM). Specify channelId OR userId. |
| discord_get_unreadA | Get messages you haven't seen yet. Uses local cache when daemon is running. |
| discord_searchB | Full-text search across locally cached Discord messages (requires daemon). |
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 8 tools
Each tool targets a distinct operation: listing DMs, getting messages, getting unread, listing channels, listing guilds, resolving user to DM channel, searching, and sending. No two tools have overlapping purposes.
All tools follow a consistent 'discord_verb_noun' pattern in snake_case, using imperative verbs (get, list, resolve, search, send). No mixing of conventions.
8 tools is well-scoped for a Discord MCP, covering essential read operations (messages, channels, guilds) and sending. Not excessive nor too sparse.
Covers core reading and sending, but lacks update/delete message operations and guild management. Minor gaps that agents can work around.