t1k:comms-mcp:discord
| Field | Value |
|---|---|
| Module | discord |
| Version | 0.5.2 |
| Effort | low |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:comms-mcp:discordDiscord (comms-mcp)
Section titled “Discord (comms-mcp)”Send and read messages in Discord text channels through an MCP server.
Source
Section titled “Source”The server is the hosted The1Studio/discord-mcp (see MCP Tools). It is not built or installed
locally: there is no setup script for it.
When to Use
Section titled “When to Use”- Posting notifications/alerts to a Discord channel from an agent
- Reading recent channel history (author / content / timestamp)
- Wiring Discord into a comms workflow
Covers text channels and threads. The hosted server (mcp__discord-mcp__*) also exposes forum
posts, Components V2, and attachment uploads; voice and DMs are not covered by this skill.
No local install. The tools are available as mcp__discord-mcp__* when the hosted server is
registered in your Claude Code MCP config (server name discord-mcp, endpoint
https://discord-mcp.the1studio.org/mcp). If the tools are missing, check that entry; access and
auth are granted by the server owner. Never paste a bot token into a repo or a chat.
Bot prerequisites (Discord Developer Portal, for the bot the hosted server uses):
- The bot token is held by the server owner, not by you.
- Privileged Gateway Intent: MESSAGE CONTENT INTENT must be enabled (without it, reads return empty content).
- The bot must be invited to the server with View Channels, Send Messages, and Read Message History. Thread and upload calls need their own permissions (see the discord-mcp gotchas ledger).
MCP Tools
Section titled “MCP Tools”The hosted server is https://discord-mcp.the1studio.org/mcp (The1Studio/discord-mcp). Its tools
appear as mcp__discord-mcp__<name>. Names use underscores, grouped by area, and take channel_id
(a snowflake), not a channel name. Names verified against packages/mcp-core/src/tools/.
| Tool | Key params | Purpose |
|---|---|---|
messages_send | channel_id (req), content (opt, max 2000), attachments (opt), message_reference (opt) | Send to a channel or thread |
messages_read | channel_id (req), limit (opt, 1-100, default 50) | Read recent messages |
messages_create_thread | channel_id (req), name (req, 1-100), message_id (opt), auto_archive_duration (opt) | Create a thread (anchored to a message, or standalone) |
attachments_prepare_upload | channel_id (req), files (1-10 of {filename, file_size}) | Get one-time upload URLs for a local file (see t1k-comms-mcp-media-upload) |
components_v2_send | channel_id (req), components (req, non-empty array) | Send a Components V2 message (e.g. MediaGallery) |
Sending files: use the t1k-comms-mcp-media-upload skill (Path A).