Skip to main content
Glama
cindiekinzz-coder

Discord MCP Extended

by cindiekinzz-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Discord MCP Extended

No user-submitted related servers found.

    Related Servers

    • neuron

      alii
      A
      license
      Not graded
      quality
      C
      maintenance
      A Discord MCP server that gives AI agents full control of a Discord bot — messages, channels, roles, threads, forums, events, webhooks, reactions, moderation, image generation, and real-time voice.
      74
      6
      MIT

    • halobot

      anthony-maio
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to communicate with humans through Discord. Agents can send messages, create threads, wait for replies, and manage conversations across any MCP client.
      16
      ISC

    • Crow

      Hydr46605
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that gives AI agents first-class access to Discord, enabling discovery, messaging, channel management, moderation, and arbitrary REST calls through typed, consent-aware tools.
      7
      3
      MIT

    • discord-admin-mcp

      kfus
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to manage Discord servers, including roles, channels, members, messages, and moderation, via natural language commands.
      1
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 26 tools

    Disambiguation5/5

    All tools have clear resource-action pairs, such as category vs channel vs webhook vs message operations. Even overlapping actions like send are distinguished by medium: text channel, webhook, or voice. The only minor overlap is add_reaction vs add_multiple_reactions, but they serve distinct purposes.

    Naming Consistency4/5

    Tools follow a consistent discord_verb_noun pattern with clear verbs like create, delete, and send. However, retrieval actions use mixed verbs: get (get_server_info), list (list_servers), and read (read_messages), which is a minor deviation. Overall, the naming is predictable and readable.

    Tool Count2/5

    With 26 tools, this exceeds the recommended range and falls into the 'too many' category. While each tool covers a distinct Discord feature, the count feels heavy and some tools could be merged (e.g., add_multiple_reactions with add_reaction). The extended scope justifies some volume, but 26 is on the high side.

    Completeness3/5

    The tool surface covers core operations for categories, text channels, forums, webhooks, messages, and reactions. However, obvious gaps exist: no update operation for text channels or messages, and no channel-specific detail retrieval beyond server info. CRUD coverage is incomplete for certain resources, limiting full workflow automation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources