Discord agent integration: Bot Token vs. OAuth2 trade-offs
Understand the story
Community discussion around how to build AI agents for Discord has centered on the choice of interface. Discord has no official MCP server, and community options either use a bot token or a self-bot user token, which Discord's terms prohibit. OAuth2 user tokens only cover identity information; messages, threads, and moderation actions have to go through a bot token, so most Discord agents actually run as bots. Earlier discussion also covered the Scalekit approach and compared when to use Bot Token versus OAuth2. The current state of things: with no official MCP server, bot tokens are the de facto channel for messaging and moderation, while OAuth2 handles only the identity part.
Generated by AI from reports · Updated 2 days ago
Report timeline
Follow the reports to explore different perspectives.
- DEV Community · MCP用 MCP 还是 API 构建 Discord Agent？两种接口的取舍
Discord 没有官方 MCP server，社区方案要么用 bot token，要么用被 Discord 条款禁止的 self-bot 用户 token。OAuth2 用户 token 只能覆盖身份信息，消息、线程和审核操作必须走 bot token，因此多数 Discord agent 实际以 bot 身份运行。
Interest in this story
Current interest 3·Peak within comparable coverage 9（Oct 5, 15:00）·Change over 24 hours within comparable coverage -50%
The trend compares the same participants under continuous, complete observation, so its coverage may be narrower than the current score. Hover or tap to view hourly interest; use the left and right arrow keys to navigate.