Discord Message Finder MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISCORD_BOT_TOKEN | Yes | Discord bot token | |
| DISCORD_DEFAULT_GUILD_ID | No | Optional default guild ID | |
| DISCORD_ALLOWED_GUILD_IDS | No | Optional comma-separated allowlist of guild IDs |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_discord_accessA | Check whether the Discord bot token works and whether a guild can be read. |
| list_guild_channelsB | List Discord guild channels and active threads so the assistant can identify where to search. |
| search_guild_messagesB | Search Discord guild messages with native Discord search. Best for finding where a past discussion happened. |
| find_in_recent_historyA | Scan recent channel history locally. Useful when native Discord search indexing is delayed or a bounded recent search is needed. |
| locate_messageC | Locate one exact Discord message from a jump URL or channel/message IDs. |
| get_message_contextB | Fetch one Discord message plus surrounding messages before and after it. |
| read_channel_messagesC | Read messages from a Discord channel with before/after/around pagination. |
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 7 tools
Each tool serves a distinct purpose: access check, channel listing, two search methods (native and recent history), reading with pagination, context retrieval, and message location from URL. There is no functional overlap that would cause confusion for an agent.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_discord_access, list_guild_channels, search_guild_messages), making it predictable for an agent to infer functionality.
With 7 tools, the server is well-scoped for its domain of Discord message finding. Each tool addresses a core operation without redundancy or unnecessary complexity.
The tool surface covers the full lifecycle of message discovery: access verification, channel enumeration, multiple search methods, paginated reading, context around a message, and pinpoint location from a URL. No obvious gaps are present.