Free for 30 days on Scale.Start free
Build10 steps1-3 weeks (most of it Discord verification queue)

Build a Discord bot and verify it

Your Discord bot live, verified, with all required Privileged Intents approved, hosted with the right gateway resilience, and a path past the 100-server cap.

Open in DockSee every step →

Your Discord bot live

Your Discord bot live, verified, with all required Privileged Intents approved, hosted with the right gateway resilience, and a path past the 100-server cap.

Spin up an agent for the heavy lifting

Reads the bot's command tree to surface every Privileged Intent the bot actually uses + every dangerous command for the verification application.

10 steps, 24 official links, 2 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

5Surfaces
10Steps
2Agent prompts
24Official links
5Tools mapped
Surfaces
  • tableSteps
  • tablePointers
  • docBot verification plan
  • tableVerification log
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/build-a-discord-bot and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

Do I need to verify my Discord bot?
Only if you want to grow past 100 servers. Below 100, you can run the bot, including with Privileged Intents, by toggling them in the Developer Portal. At 100 servers, new server adds halt and Privileged Intents lock until verification completes.
How long does verification take?
Typical: 1-3 weeks. Slower in December and around major Discord product launches. The Stripe Identity step is fast (5-10 min). The application review is the slow part. Submit before you hit 75 servers if you can — you don't want to be at 99 with a stuck application.
Can my bot run without Privileged Intents?
Yes, increasingly so. If your bot is slash-command-driven (no message-content reading), you can ship without any Privileged Intents. This used to be uncommon; since 2022 it's the recommended path. Most modern bots only request privileged intents if a feature literally cannot exist without them.
Why is my bot not responding to messages?
Three checks in order: (1) does your bot have permission in the channel (Send Messages + Read Message History)? (2) does the bot's gateway client have the right intents (Guilds is mandatory; MESSAGE_CONTENT for reading message bodies)? (3) is your gateway worker actually online? Run a /ping slash command first to isolate.
Can my AI agents help with the Discord bot?
Yes. Agents are particularly useful for: drafting the verification application (intent justifications, command summaries, data handling), reading the source to find every Privileged Intent the code actually uses, drafting the Privacy Policy + ToS pages from a data audit, monitoring server count + nudging when verification deadlines approach. The template ships agent prompts inline.
Related templates

More from Build

BuildMixed
Launch your iPhone app on the App Store

10-step plan from 'I have a build on my Mac' to 'users are downloading from search.' Real Apple gates, real gotchas, real agent prompts.

BuildMixed
Build a webapp in a day

10-step plan from blank idea to deployed app with auth, a database, and a domain — all in 24 hours. Battle-tested defaults so you don't waste 6 hours picking a stack.

BuildMixed
Launch your Android app on Google Play

10-step plan from 'I have an APK on my laptop' to 'users are installing from Play search.' Real Google gates, real gotchas, real agent prompts.

Browse all Build templates →
Used by these teams · 1

Teams that run this template, with their full setup.

Open-source maintainersUse case

Triage your issue queue without losing your weekend.

Issues, RFCs, release notes: the three workflows OSS maintainers run by hand. Agents read new issues, attempt repro, label, and surface duplicates. The RFC doc replaces a sprawling GitHub thread.

Open the use case

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.