Skip to content

Guides

Choose the outcome closest to your task. Each guide shows the tool sequence, request and response shapes, safety boundary, and partial-failure behavior. For a single contract, use the tool reference.

Stop a raid

Find raid accounts with members_search, confirm with the human, ban up to 200 users in one call. Covers __confirm:true and partial failure handling.

Read recipe →

Build a rich announcement

Compose a launch announcement from sections, a media gallery, and a container; validate before sending; understand the flags = 32768 requirement.

Read recipe →

Chain three calls

Use mcp_pipeline to announce, schedule an event, and grant a role in one request. Covers {{step.path}} interpolation and the recursion guard.

Read recipe →

Summarize a busy channel

Use MCP sampling to summarize the last 50 messages without an LLM API key. Covers the host_llm_should_process fallback for clients without sampling.

Read recipe →

Publish as a webhook

Provision a webhook once, then post high-volume notifications without consuming the bot’s bucket. Covers token security and Components V2 over webhooks.

Read recipe →

Verify a Gateway notification

Verify resources/subscribe notifications backed by Discord Gateway events. Covers the five notification URI keys, debounce, REST-only fallback, and the current lack of resource list/read handlers.

Read recipe →

  • Tool calls are shown as the JSON-RPC tools/call argument shape - the name and arguments fields. Wrap them in your client’s tools/call envelope as needed.
  • Snowflake IDs in examples are realistic 18–19 digit Discord IDs, not placeholder integers. Substitute your own when adapting.
  • Output shapes match what the server actually returns, including the untrusted_* envelopes for user-controlled fields.
  • Internal links use the /discord-mcp/ prefix because the docs site is served from a base path on GitHub Pages.
  • Single tool reference → Tools (192 auto-generated pages).
  • Operational concerns (deploy, observability, security) → Operations.
  • How the server is built → Architecture.
  • Glossary, environment variables, error codes → Reference.