No user-submitted related servers found.
Scored across 209 tools
Per-tool descriptions are exemplary with explicit 'When NOT to use' guidance, but at 209 tools there are genuine redundancies: voice_list_regions/guild_list_voice_regions return nearly identical data, templates_get/templates_inspect overlap heavily, and templates_recommend/guild_blueprint_compile both internally select a primary template plus inspirations from the same catalog. The global/guild, with_token, and current/user paired variants multiply the surface and require careful reading to distinguish.
The dominant resource_verb convention (channels_list, members_ban, roles_modify, webhooks_execute) is applied impressively consistently across most of the 209 tools. Deviations exist: messages_read breaks the list/get pattern, mcp_pipeline and intelligence_* fit no resource convention, and voice_get_current_user_state vs guild_modify_current_voice_state split related operations across different prefixes.
209 tools is far beyond the already-heavy 25+ threshold and into the extreme range, even accounting for Discord's large API. The count is inflated by redundant pairs (duplicate voice region tools), adjacent suites (blueprint pipeline, intelligence suite, mcp_pipeline meta-tool), and niche monetization endpoints (SKUs, subscriptions, entitlements) that most agent workflows will never touch.
The server covers essentially the entire Discord REST surface with full CRUD lifecycles across channels, messages, members, roles, webhooks, commands, AutoMod, events, stickers, emojis, and more. Gaps exist: invites_list_channel references a missing guild_list_invites tool, standalone thread creation is deferred 'once available', and there's no dedicated file/attachment upload tool for bot messages.