Skip to main content
Glama
cappyeo

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to discord-mcp

No user-submitted related servers found.

    Related Servers

    • Discord MCP Server

      erinlkolp
      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
      -

    • Discord MCP Server

      tristan-kkim
      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

    • Discord MCP Server

      swaritsoni6-lgtm
      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

    • Discord MCP Server

      Sunwood-ai-labs
      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.
      22 npm
      1
      MIT

    • Discord MCP Server

      Kaleemullah-Younas
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to send and read messages in Discord channels, manage servers, channels, and roles via Discord's API.
      16 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 221 tools

    Disambiguation2/5

    Multiple tools overlap heavily, especially around sending/editing messages (messages_send, messages_publish, messages_compose, messages_update, messages_edit, components_v2_send, webhooks_execute), permissions auditing (permissions_audit_channel, permissions_explain, permissions_member_access_report), and voice regions (voice_list_regions vs guild_list_voice_regions). While descriptions include cross-references and 'When NOT to use' guidance, the sheer number of tools with adjacent purposes creates frequent boundary ambiguity.

    Naming Consistency4/5

    Most tools follow a predictable snake_case domain-prefix + action pattern (messages_send, channels_create_guild_channel, roles_modify, members_ban). Some deviations exist, such as noun-phrase names (guild_change_plan, mcp_pipeline, discord_intent_plan, guild_blueprint_compile, components_v2_build_container), but these are minor relative to the overall consistency.

    Tool Count1/5

    221 tools is an extreme mismatch for any MCP server, far exceeding the 50+ threshold where coherence collapses. Even for a comprehensive Discord API wrapper, this volume makes tool selection error-prone and unmanageable.

    Completeness4/5

    The surface covers a very broad range of Discord resources: guilds, channels, messages, roles, members, webhooks, emojis, stickers, application commands, interactions, AutoMod, templates, stage instances, soundboard, polls, and entitlements. Minor gaps exist (e.g., no general voice connection join/leave tool despite soundboard_send_sound requiring it), but most CRUD and lifecycle operations are present.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources