Discord MCP Server
A Model Context Protocol (MCP) server that provides Discord integration capabilities to MCP clients like Claude Desktop.
Available Tools
Server Information
get_server_info: Get detailed server informationlist_members: List server members and their roles
Message Management
send_message: Send a message to a channelread_messages: Read recent message historyadd_reaction: Add a reaction to a messageadd_multiple_reactions: Add multiple reactions to a messageremove_reaction: Remove a reaction from a messagemoderate_message: Delete messages and timeout users
Channel Management
create_text_channel: Create a new text channeldelete_channel: Delete an existing channel
Role Management
add_role: Add a role to a userremove_role: Remove a role from a user
Webhook Management
create_webhook: Create a new webhooklist_webhooks: List webhooks in a channelsend_webhook_message: Send messages via webhookmodify_webhook: Update webhook settingsdelete_webhook: Delete a webhook
Installation
Installing via Smithery
To install Discord Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @hanweg/mcp-discord --client claude
-
Set up your Discord bot:
- Create a new application at Discord Developer Portal
- Create a bot and copy the token
- Enable required privileged intents:
- MESSAGE CONTENT INTENT
- PRESENCE INTENT
- SERVER MEMBERS INTENT
- Invite the bot to your server using OAuth2 URL Generator
-
Clone and install the package:
# Clone the repository
git clone https://github.com/hanweg/mcp-discord.git
cd mcp-discord
# Create and activate virtual environment
uv venv
.venv\Scripts\activate
### If using Python 3.13+ - install audioop library: `uv pip install audioop-lts`
# Install the package
uv pip install -e .
- Configure Claude Desktop (
%APPDATA%\Claude\claude_desktop_config.jsonon Windows,~/Library/Application Support/Claude/claude_desktop_config.jsonon macOS):
"discord": {
"command": "uv",
"args": [
"--directory",
"C:\\PATH\\TO\\mcp-discord",
"run",
"mcp-discord"
],
"env": {
"DISCORD_TOKEN": "your_bot_token"
}
}
License
MIT License - see LICENSE file for details.
Metadata
Release files for mcp-discord 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_discord-0.1.0.tar.gz | 48.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_discord-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 57.3 kB
Release files / mcp_discord-0.1.0.tar.gz
| Download URL | mcp_discord-0.1.0.tar.gz |
|---|---|
| Size | 48.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45166b0f1efad1fe4c94c4870d2c95664bbc5e18da2f2603e57558852dabadb3
|
|
BLAKE2b-256 checksum How to use checksums |
785e50ac1321ff787221b6eb4b7cd4c0271986994abef8e601d0e26123db417e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.10
|
Release files / mcp_discord-0.1.0-py3-none-any.whl
| Download URL | mcp_discord-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3cc68016a2a2ef02b45fd4e9720ff2f60c2570265af5543ad810cb920b9b373
|
|
BLAKE2b-256 checksum How to use checksums |
c17e668bae900bdb2e7a02536e4a7ca68decc8708e1d6995c311da23e2a49403
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.10
|
Security for mcp-discord 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.