# Discord MCP (io.github.cappyeo/discord-mcp@0.27.0)

> Source: <https://mcpindex.ai/server/io-github-cappyeo-discord-mcp>
> Published: 2026-09-14 16:03:31+00:00

[← Index](/leaderboard)

# Discord MCP

Caller-owned Discord operations for AI agents with 209 typed tools and verifiable guild builds.

The current version, v0.27.0, was published to the official MCP registry on 2026-09-14. It is distributed as @discord-mcp/cli on npm, filed under Chat & Messaging by this index, and declares 3 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context.

## Using Discord MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that).

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

```
uv tool install mcpindex-gate && mcpindex-config-wire
```

[method](/methodology)

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

`mcpindex.integrity.description` passINFO
evidence“No malicious instructions”via static_description

- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? [Screen its description →](/screen)

## That verdict was true at screening time (snapshot 2026-09-14).

Contracts can change after screening, with no version bump. The gate pins Discord MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

[See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold)

Related: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift)

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

```
[Independent trust record for Discord MCP](https://mcpindex.ai/server/io-github-cappyeo-discord-mcp) - screening verdict, registry provenance, and contract drift monitoring.
<a href="https://mcpindex.ai/server/io-github-cappyeo-discord-mcp">Independent trust record for Discord MCP</a> - screening verdict, registry provenance, and contract drift monitoring.
```

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

```
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-cappyeo-discord-mcp)](https://mcpindex.ai/server/io-github-cappyeo-discord-mcp)
<a href="https://mcpindex.ai/server/io-github-cappyeo-discord-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-cappyeo-discord-mcp" alt="mcpindex verdict" height="20" /></a>
```

`DISCORD_TOKEN`
Discord bot token. The optional Bot prefix is accepted.

`DISCORD_EXPECTED_BOT_ID`
Expected Discord bot ID. Startup fails if the token belongs to another bot.

`ALLOWED_GUILDS`
Comma-separated Discord guild IDs this deployment may operate against.

[methodology](/methodology)

[GuildControl MCPapp.lasers.guildcontrol/discord](/server/app-lasers-guildcontrol-discord)

Safety-first MCP server for Discord with privacy-safe reads, audits, and reviewed administration

[Cavyrocom.cavyro/cavyro](/server/com-cavyro-cavyro)

Telegram-native CRM for agents: contacts, deals, pipelines, campaigns, docs and reports.

[RevDesk Product MCPio.github.cell-labs-inc/revdesk-product](/server/io-github-cell-labs-inc-revdesk-product)

Give AI agents secure access to RevDesk calling, SMS, phone numbers, caller IDs, and usage.
