Skip to main content
Glama
cappyeo

discord-mcp

Related Servers

Alternatives to discord-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Discord by managing servers, channels, forum posts, messages, reactions, webhooks, roles, and members through the Model Context Protocol.
      733 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables direct interaction with Discord servers to send messages, read channel history, and post rich embeds through natural conversation. It provides tools for listing channels and managing communication within Discord guilds using the Model Context Protocol.
      4
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with Discord through the Model Context Protocol, providing access to all Discord features like channels, messages, threads, reactions, and roles. Supports secure Discord bot operations with rate limiting, caching, and comprehensive API coverage for OpenAI, LangChain, and other MCP clients.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Discord through the REST API, supporting message reading and sending, channel and guild management, threads, pins, and reactions.
      17
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Discord through the REST API and real-time events, supporting message management, user info, channel operations, and more with security controls.
      4 npm
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 222 tools

    Disambiguation3/5

    Most tools carry explicit 'When to use' / 'When NOT to use → use X' guidance, which makes the vast majority of the 222 tools distinguishable in practice. However, several families genuinely overlap: templates_recommend vs guild_blueprint_compile vs guild_blueprint_plan all turn a natural-language request into a server blueprint, and messages_send vs components_v2_send vs messages_publish vs webhooks_execute vs interactions_* all deliver content. The dense cross-references mitigate but do not remove this ambiguity.

    Naming Consistency4/5

    The dominant pattern is consistent snake_case resource_action (messages_send, channels_delete, roles_modify, automod_get_rule), applied across nearly the entire surface. Minor deviations exist in deeply qualified names and outliers like discord_intent_plan, mcp_pipeline, inspiration_emoji_gg_search, and channels_list_active_threads_guild, but nothing chaotic.

    Tool Count1/5

    222 tools for a single Discord integration is an extreme mismatch by any standard and far beyond the 3-15 range that keeps an agent's selection accurate. Whole clusters (blueprint planning, workflow, components V2 build/validate/send/edit, four separate archived-thread listers, bot-auth and token-auth webhook variants) inflate the surface well past what a scoped server should expose.

    Completeness5/5

    Coverage is exhaustive: full CRUD/lifecycle for messages, channels, threads, roles, members, webhooks, emojis, stickers, invites, AutoMod, events, commands, stage instances, soundboard, polls, onboarding, SKUs/subscriptions/entitlements, plus audit, permission explanation, and higher-level orchestration. Read, mutate, verify, and confirmation paths are all represented with very few dead ends.

    Maintenance

    ActivityActive
    ResponsivenessSlow