No self-bots
Automating a normal user account outside the OAuth2/bot API is forbidden and can lead to account termination. Use a bot application. [6]
Guides · social · Verification-gated
Create an application in the Discord Developer Portal, copy its application id and public key, reset and copy the bot token (shown once), set install contexts and an install link. Growing past 100 servers needs app verification (team owner identity check), and privileged intents need a review above 10,000 users.
Researched · not yet run liveLast researched 25 October 2026 · Discord · provider site
A Discord user account signs in to the Developer Portal and creates applications. Apps can be owned by the user or by a developer Team; for verification the Team owner is the person whose identity is checked. Each application has a bot user and its own token.
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Sign in yourself with your Discord account.
Where: https://discord.com/developers/applications
Create a developer Team to own the app, so the app is not tied to a single personal account. The Team owner is who verifies identity later.
New Application, enter a name and press Create yourself (accept any terms shown). Copy the Application ID and Public Key from General Information.
verapli captures DISCORD_APPLICATION_ID here by plain code: encrypted in your browser, never shown to AI.
Where: https://discord.com/developers/applications
On the Bot page click Reset Token and copy it immediately; it is shown only once. verapli writes it only to your own env file.
On Installation choose User Install and/or Guild Install, pick the Discord Provided Link, add applications.commands (and bot plus needed permissions for guild installs), then open the link to add the app.
Below 10,000 users you can toggle privileged intents (e.g. message content) in the portal yourself. Prefer interactions/slash commands where possible.
Once eligible (about 76 servers), apply for verification in the portal. The Team owner verifies identity through Stripe. Unverified apps cannot join more than 100 servers.
When notified, apply within 90 days with a justification for each intent and how you handle the data. Reapply once a year.
Plain-English summary, not legal advice. Each card links its source.
Automating a normal user account outside the OAuth2/bot API is forbidden and can lead to account termination. Use a bot application. [6]
Verification is required for apps in 100+ guilds, and the Team owner must pass an identity check. [2]
Above 10,000 users privileged intents need review, with annual reapplication; missing the 90-day window removes access. [3]
After verification, Team ownership cannot be transferred [to verify current rule]. [5]
| Env var | Secret | Format | What it is |
|---|---|---|---|
DISCORD_APPLICATION_ID | not secret | Application (client) id | |
DISCORD_PUBLIC_KEY | not secret | Public key used to verify interaction requests | |
DISCORD_BOT_TOKEN | secret | Bot token (shown once; reset to replace) |
The same entry as JSON: /api/v1/entries/discord/developer-app · requirements /api/v1/requirements/discord/developer-app · terms /api/v1/terms/discord/developer-app.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Discord developer app and bot (with verification and privileged intents), and how long will it take?"
→ tools/call requirements { "provider_id": "discord/developer-app" }Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Discord is not affiliated with verapli.