discord-support-mcp
Enables AI agents to manage Discord support tickets by listing, reading, replying to, renaming, and closing ticket channels, with PII redaction for self-hosted compliance.
README
discord-support-mcp
An MCP server that exposes Discord support tickets as tools for AI agents. Built for servers that manage tickets with Ticket Tool (which has no public API): it reads the ticket channels directly through the Discord bot API.
Tools
| Tool | What it does |
|---|---|
list_open_tickets |
Lists channels in the configured ticket category, oldest first |
read_ticket |
Returns recent message history of a ticket |
reply_to_ticket |
Posts a message into a ticket as the bot |
rename_ticket |
Renames a ticket channel |
close_ticket |
Locks + renames a ticket (closed- prefix) |
list_members |
Username substring lookup (respects PII_REDACT) |
Compliance / self-hosting
If agents touching user-identifying information must be self-hosted, run this
server on your own infrastructure next to your self-hosted model and set
PII_REDACT=true. All message content is then stripped of emails, phone
numbers, mentions and snowflake IDs before it reaches any upstream (cloud)
agent. Only the sanitized layer should be exposed beyond the host.
Setup
- Create a bot at https://discord.com/developers/applications
- Enable Message Content Intent and Server Members Intent.
- Invite with scopes
botand permissions: View Channels, Read Message History, Send Messages, Manage Channels, Manage Roles (for close).
- Find the category ID Ticket Tool puts tickets in (right-click the category in Discord with developer mode on → Copy Channel ID).
- Configure:
cp .env.example .env # fill in values
npm install
npm run build
- Wire into an MCP client (e.g. Claude Desktop config):
{
"mcpServers": {
"discord-support": {
"command": "node",
"args": ["/absolute/path/to/discord-support-mcp/dist/index.js"],
"env": {
"DISCORD_TOKEN": "...",
"GUILD_ID": "...",
"TICKET_CATEGORY_ID": "...",
"PII_REDACT": "true"
}
}
}
}
Notes
close_ticketis a safe archive (lock + rename). Actual transcript/deletion stays with Ticket Tool's own/closeso your transcripts channel keeps working; the agent can also just call Ticket Tool's close command flow manually for now.- Discord rate limits apply; history reads are capped at 100 messages per call.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.