Dis.gg MCP Docs

Dis.gg MCP Documentation

Dis.gg MCP is a hosted MCP service that lets MCP-compatible clients call Discord through a Discord bot token.

In plain English: it gives AI tools a controlled way to use Discord. Instead of only chatting about Discord, an AI assistant can actually look at channels, read messages, create replies, manage server objects, use webhooks, schedule reminders, and more, depending on the permissions you choose to give it.

Use it when you want an AI client, Discord bot, automation agent, or internal tool to read or act in Discord without building and operating your own Discord MCP server.

Simple Examples #

With Dis.gg MCP, you can build workflows such as:

  • ask an AI assistant to summarize recent messages in a support channel,
  • let a coding agent check project discussions before making a change,
  • give a Discord bot the ability to inspect channels, threads, roles, invites, events, or webhooks before answering,
  • create controlled automation for reminders, threads, or moderation tasks,
  • test Discord AI workflows before committing to a custom backend,
  • use one standard MCP connection from clients such as Codex, Claude Code, or an app built with the OpenAI SDK.

For a Discord bot with AI, this is the important part: connecting the MCP can turn a basic chatbot into an assistant with real Discord tools. A normal chatbot can only answer from its prompt and conversation history. A bot backed by an AI model plus Dis.gg MCP can, with the right Discord permissions and MCP restrictions, inspect the server, find the relevant context, act on channels or messages, and use Discord features directly.

For example, a bot using the OpenAI SDK, another AI SDK, or an MCP-compatible agent framework can connect to Dis.gg MCP and expose only the tools it needs. You can start with read-only access, then add write, moderation, webhook, or scheduling tools when the workflow is ready.

What It Is For #

Discord has many features, but most AI clients cannot use them directly in a controlled way. Dis.gg MCP provides a stable MCP interface in front of Discord so a client can call Discord tools without each project reinventing the same bridge.

The service is useful when you need Discord access from:

See more example clients: https://modelcontextprotocol.io/clients

Who It Is For #

Dis.gg MCP is designed for people who already have a Discord bot or are comfortable creating one:

  • developers connecting coding agents to project Discord servers,
  • server operators who want controlled automation without writing a full bot,
  • support or community teams that need read, search, reply, or moderation workflows,
  • product teams testing Discord integrations before building custom backend logic,
  • power users who want a standard MCP endpoint instead of one-off scripts.

It is not a replacement for your own product logic, moderation policy, or Discord permission model. You still decide which bot token is used, which Discord permissions it has, which tools your client may call, and when human approval is required.

Problems It Solves #

Fast Discord Access From AI Clients #

You can connect a client to https://mcp.dis.gg/v1, pass a Discord bot token, and start with read-only tools before enabling higher-impact actions. This avoids writing a custom MCP server just to answer questions such as:

  • what happened in a channel,
  • which guilds and channels are available,
  • whether a message, thread, role, invite, event, or webhook exists,
  • what changed recently in a server.

Safer Automation Boundaries #

LLM tool use needs more than a token. Dis.gg MCP supports request-time restrictions through headers, so the same Discord bot token can be constrained for a specific workflow, target guild, channel set, permission bitmask, or allowed action surface.

These restrictions complement client-side tool allowlists such as OpenAI allowed_tools or Claude Code --allowedTools.

Broader Discord Coverage #

Many Discord MCP examples focus on a small set of message tools. Dis.gg MCP is built around wider Discord REST coverage, including messages, channels, threads, roles, members, emojis, invites, scheduled events, webhooks, auto moderation, local MCP settings, reminders, and provider-backed media workflows.

Hosted Operation #

If you do not want to maintain a custom MCP service, Dis.gg MCP gives you a public endpoint with consistent docs, tool metadata, JSON-RPC support, legacy SSE compatibility, and service-level safeguards.

Why Use Dis.gg MCP #

Choose Dis.gg MCP instead of a local or custom Discord MCP when you want:

  • a hosted endpoint rather than another service to deploy,
  • broad Discord tool coverage out of the box,
  • documented restriction headers for safer use with LLMs,
  • compatibility with common MCP clients,
  • stable public documentation and tool discovery,
  • clear separation between client-side allowlists, MCP-side restrictions, and Discord's own permission system.

A custom MCP can still be the right choice when you need private business logic, bespoke approval flows, unusual data retention rules, or an integration that should never leave your infrastructure.

Common Starting Points #

  • Quickstart: prepare a Discord bot token and connect a client quickly.
  • Examples: see small companion projects that use the service.
  • Usage: understand the endpoints, request flow, and common patterns.
  • Headers: apply Discord MCP-side restrictions before a request reaches Discord.
  • Security: review the guardrails and deployment advice.
  • Changelog: follow public-facing updates to the service.

Recommended First Setup #

  1. Create a Discord application and bot token.
  2. Give the bot only the Discord permissions your workflow needs.
  3. Connect your MCP client to https://mcp.dis.gg/v1.
  4. Start with read-only tools.
  5. Add client-side tool allowlists.
  6. Add MCP restriction headers for guild, channel, user, and permission scope.
  7. Enable write or moderation tools only after testing the workflow.

Reference #

  • Tools: public tool catalog by category.
  • Providers: image and upload providers supported by the service.
  • About: what the service is for, and what it does not do.

Legal #

Service Endpoints #

  • JSON-RPC: POST /v1
  • Tool list helper: GET /v1/tools/list
  • Tool call helper: POST /v1/tools/call
  • Legacy SSE stream: GET /v1/sse
  • Legacy SSE message ingress: POST /v1/sse/message?sessionId=...
  • Health check: GET /healthz
  • Support redirect: GET /support