# Discord

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

- name: io.github.mcp-dir/discord-mcp
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 91/100
- quality: 88/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.mcp-dir%2Fdiscord-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.mcp-dir%2Fdiscord-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "discord-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_discord"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 85
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-97% ~updated-60d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 88/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 21 of 21 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 3,312 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 21, about 3,312 tokens to load them all
- tool set hash: ce1595610f5d22235fac636c8dba50d4
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.mcp-dir/discord-mcp.svg)](https://protogrid.dev/servers/io.github.mcp-dir/discord-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://api.mcp.ai/p_discord (streamable-http, auth none, reachable true, uptime30d 0.9741379)

## Packages

_none_

## Tools (21)

- `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.
- `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.
- `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.
- `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_get_channel`: Get a channel's metadata (type, name, topic, parent, permissions).

Bulk support: accepts channel_ids for batched execution.
- `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_get_me`: Return the bot's own user profile (id, username, discriminator, avatar, etc).
- `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_list_accounts`: List Discord bot connections linked to this install — id, label, default guild_id.
- `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_list_guilds`: List the servers (guilds) the bot is a member of.
- `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_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_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.
- `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; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
- `report_bug`: Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
- `show_version`: Show the current MCP platform and adapter versions.
- `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.