io.github.mcp-dir/discord-mcp

Discord

Connect a Discord bot (bot token from the developer portal) to read/send messages, list guilds and c

0.1.0
Version
remote
Transport
21
Tools

Security review

Review passed

Reviewed 20h ago.

  • tools: 21 tools scanned
  • metadata: scanned

No findings.

Tools (21)

  • discord_list_accounts

    List Discord bot connections linked to this install — id, label, default guild_id.

  • discord_get_me

    Return the bot's own user profile (id, username, discriminator, avatar, etc).

  • discord_list_guilds

    List the servers (guilds) the bot is a member of.

  • discord_get_guild

    Get one guild's metadata. Falls back to the connection's default guild_id. Bulk support: accepts guild_ids for batched execution.

  • discord_list_channels

    List channels in a guild. Falls back to the connection's default guild_id. Bulk support: accepts guild_ids for batched execution.

  • discord_list_guild_members

    List members of a guild. Requires the bot to have the Server Members intent enabled in the developer portal — may return 403 otherwise. Bulk support: accepts guild_ids for batched execution.

  • discord_get_channel

    Get a channel's metadata (type, name, topic, parent, permissions). Bulk support: accepts channel_ids for batched execution.

  • discord_list_messages

    Read recent messages from a channel (newest first). Pagination via `before` / `after` / `around` (message ids). Requires Message Content intent for non-bot message bodies in some cases. Bulk support: accepts channel_ids for batched execution.

  • discord_get_message

    Fetch a single message by id. Bulk support: accepts channel_ids, message_ids for batched execution.

  • discord_get_user

    Public profile of any Discord user by id. Bulk support: accepts user_ids for batched execution.

  • discord_send_message

    Post a message to a channel. Provide `content` (text up to 2000 chars), `embeds` (rich JSON), or both. `reply_to` makes it a reply. Bulk support: accepts channel_ids for batched execution.

  • discord_send_dm

    Open a DM channel with a user and send them a message. The bot and the user must share a guild. Bulk support: accepts user_ids for batched execution.

  • discord_edit_message

    Edit a previously-sent message (must be authored by this bot). Bulk support: accepts channel_ids, message_ids for batched execution.

  • discord_add_reaction

    Add a reaction to a message. `emoji` is either unicode (e.g. `👍`) or `name:id` for custom guild emoji. Bulk support: accepts channel_ids, message_ids for batched execution.

  • discord_delete_message

    Delete a message. Irreversible. Bot needs Manage Messages to delete messages authored by other users. Bulk support: accepts channel_ids, message_ids for batched execution.

  • show_version

    Show the current MCP platform and adapter versions.

  • report_bug

    Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

  • connect

    Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

  • toolkit_info

    Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

  • marketplace

    The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing;

  • authenticate

    MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.