Discord Bridge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISCORD_GUILD_ID | Yes | Discord server (guild) ID | |
| DISCORD_BOT_TOKEN | Yes | Discord bot token | |
| DISCORD_DEFAULT_CHANNEL | No | Default channel name (defaults to "general") | general |
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_sendC | Send a message to a Discord channel. |
| discord_readC | Read recent messages from a Discord channel. |
| discord_replyC | Reply to a specific Discord message. |
| discord_reactC | Add a reaction emoji to a Discord message. |
| discord_channelsB | List all text channels in the Discord server. |
| discord_check_mentionsC | Check for recent messages that mention the bot. |
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 6 tools
Each tool has a clearly distinct purpose targeting specific Discord actions: listing channels, checking mentions, reacting, reading messages, replying, and sending messages. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent 'discord_' prefix with descriptive verb_noun patterns (e.g., discord_channels, discord_react, discord_send). This uniformity enhances readability and predictability across the toolset.
With 6 tools, the server is well-scoped for a Discord bridge, covering essential messaging and interaction functions without being overly sparse or bloated. Each tool serves a clear and necessary role in the domain.
The toolset provides strong coverage for core Discord messaging workflows, including sending, reading, replying, and reacting. A minor gap exists in the lack of tools for managing channels (e.g., creating or deleting) or handling other Discord features like voice channels or user management, but agents can still perform key tasks effectively.