Discord rolled out a significant overhaul of its Developer Portal and developer documentation in May 2026, and a few of the changes are particularly relevant if you build AI bots. The portal got a refreshed home page, the docs were reorganized, and most interesting for AI builders, the documentation now ships a built-in MCP server, an LLMs.txt file, and a Copy-as-Markdown button on every page. AI tooling has officially landed in Discord's developer experience.
If you run a Discord bot built on OpenClaw Launch — or any AI agent platform — here is what changed, what is new under the hood, and how it affects your day-to-day workflow.
Portal Refresh: Cleaner Navigation and Auto-Localization
The main Developer Portal got a redesigned home screen with quick access to your apps and the docs. Discord also added improved light and dark mode support and automatic localization that matches the language set in your Discord client. None of this changes the API surface, so your existing bots keep working, but day-to-day app management is noticeably less friction-y.
Existing doc URLs remain stable. Discord explicitly chose not to break old deep links during the reorganization, so any tutorials, blog posts, or internal docs pointing at discord.com/developers/docs/... keep working without redirects.
MCP Server for the Discord Docs
This is the headline change for AI builders: Discord's docs now ship a public Model Context Protocol (MCP) server. That means any MCP-capable AI agent, including the ones you deploy on OpenClaw Launch, can query Discord's documentation in real time without copy-pasting URLs into a chat window.
If you have ever asked a coding assistant how to wire up an interaction or set the right intent flag and gotten an answer that referenced the 2022 docs, this fixes it. The MCP server is the canonical, current source, so the agent gets the same answer Discord's own internal tools see.
For OpenClaw Launch users running a Discord bot, this opens up a clean pattern: connect the Discord MCP server alongside your other tools, and your bot can answer questions about its own platform's API surface from within Discord itself.
LLMs.txt and Copy-as-Markdown
Two smaller but useful additions land alongside the MCP server:
- LLMs.txt file at
discord.com/llms.txt— a curated index of the docs designed for LLM consumption. Following the emerging community standard, this gives any AI agent a single endpoint to fetch a clean overview of what is available without scraping nav chrome. - Copy-as-Markdown button on every doc page — one click to grab the page content as clean Markdown, ready to paste into a Claude, GPT, or Gemini context window. No more manually stripping headers, footers, and rewriting tables.
Both changes recognize that a meaningful chunk of "developer reading the docs" is now actually "an AI assistant reading the docs on the developer's behalf." Discord is one of the first major platforms to officially design for this case rather than treat it as an unintended use of their site.
Reorganized Documentation
The docs themselves got new feature-area tabs and overview sections covering platform-wide behavior. There is now a clearer separation between API reference, conceptual guides, and use-case walkthroughs. If you have struggled to find where Discord documents a specific gateway event or interaction subtype, the new tab and sidebar layout should help.
Not affected: anything you already knew about Discord's API. Intents still work the same way, the gateway protocol is unchanged, and your existing bot tokens are untouched. This is a documentation and developer-experience update, not an API change.
Claim Your Game and Verified Servers
Discord also rolled out a new "Claim Your Game" flow that lets game developers customize their game profile on Discord and earn a verified check on their server. This is targeted at game studios more than AI bot builders, but it is worth knowing about if you ship a bot tied to a game community — the verified check is a trust signal for users joining the server for the first time.
What This Means for OpenClaw Launch Users
Practical takeaways if you run a Discord bot on OpenClaw Launch:
- Your bot keeps working. No API changes, no required updates, no token rotations.
- The Discord MCP server is worth wiring up if your bot answers Discord-meta questions like moderation help, channel setup advice, or slash command authoring tips. It pairs naturally with the OpenClaw skill ecosystem.
- Copy-as-Markdown saves time when feeding Discord docs to your AI for skill or plugin authoring, or when troubleshooting an interaction handler.
- The new portal home page is mostly a nicer place to manage your bot's application. Bookmark it and forget about the old layout.
The Bigger Picture: Docs Designed for Agents
Discord's portal refresh is a small but telling change. The platforms we build on are increasingly designing for AI assistants as first-class consumers of their docs, not only human developers. MCP server, LLMs.txt, and Copy-as-Markdown are three different angles on the same idea: make it trivial for an agent to read your docs correctly and act on them. Expect more of this from major SaaS APIs over the rest of 2026.
Get Started
If you do not have a Discord bot yet, you can deploy one in about 10 seconds from the OpenClaw Launch dashboard — pick Discord from the configurator, click deploy, and the bot is live with the new portal already wired in. For the full technical setup walkthrough, see our OpenClaw + Discord guide.