{"slug": "discord-mcp-io-github-cappyeo-discord-mcp-0-27-0", "title": "Discord MCP (io.github.cappyeo/discord-mcp@0.27.0)", "summary": "Discord MCP version 0.27.0, a server providing 209 typed tools for caller-owned Discord operations by AI agents, was published to the official MCP registry on 2026-09-14 and is distributed as @discord-mcp/cli on npm. The mcpindex registry listing reports a semantic screen found no manipulation pattern in the tool description, though the deterministic conformance probe has not yet run and the verdict is advisory with uncalibrated confidence at v1. The server declares 3 environment variables, including the required DISCORD_TOKEN bot token.", "body_md": "[← Index](/leaderboard)\n\n# Discord MCP\n\nCaller-owned Discord operations for AI agents with 209 typed tools and verifiable guild builds.\n\nThe 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.\n\n## Using Discord MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?\n\nMCP 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).\n\nRewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less\n\n```\nuv tool install mcpindex-gate && mcpindex-config-wire\n```\n\n[method](/methodology)\n\nSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.\n\n`mcpindex.integrity.description` passINFO\nevidence“No malicious instructions”via static_description\n\n- - Semantic screen only - the deterministic conformance probe has not run on this server\n- - Confidence is reported but not yet calibrated (v1)\n- - Screen reads the tool description, not the live behavior\n- - advisory\n- - registry description only no input schema\n- - screen model 8b\n- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not\n\nSemantic 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.\n\nOwn this server? [Screen its description →](/screen)\n\n## That verdict was true at screening time (snapshot 2026-09-14).\n\nContracts 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.\n\n[See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold)\n\nRelated: [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)\n\nPeople 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.\n\n```\n[Independent trust record for Discord MCP](https://mcpindex.ai/server/io-github-cappyeo-discord-mcp) - screening verdict, registry provenance, and contract drift monitoring.\nIndependent trust record for Discord MCP - screening verdict, registry provenance, and contract drift monitoring.\n```\n\nA live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.\n\n```\n[](https://mcpindex.ai/server/io-github-cappyeo-discord-mcp)\n![\"mcpindex](\"https://mcpindex.ai/api/v1/badge/io-github-cappyeo-discord-mcp\")
\n```\n\n`DISCORD_TOKEN`\nDiscord bot token. The optional Bot prefix is accepted.\n\n`DISCORD_EXPECTED_BOT_ID`\nExpected Discord bot ID. Startup fails if the token belongs to another bot.\n\n`ALLOWED_GUILDS`\nComma-separated Discord guild IDs this deployment may operate against.\n\n[methodology](/methodology)\n\n[GuildControl MCPapp.lasers.guildcontrol/discord](/server/app-lasers-guildcontrol-discord)\n\nSafety-first MCP server for Discord with privacy-safe reads, audits, and reviewed administration\n\n[Cavyrocom.cavyro/cavyro](/server/com-cavyro-cavyro)\n\nTelegram-native CRM for agents: contacts, deals, pipelines, campaigns, docs and reports.\n\n[RevDesk Product MCPio.github.cell-labs-inc/revdesk-product](/server/io-github-cell-labs-inc-revdesk-product)\n\nGive AI agents secure access to RevDesk calling, SMS, phone numbers, caller IDs, and usage.", "url": "https://wpnews.pro/news/discord-mcp-io-github-cappyeo-discord-mcp-0-27-0", "canonical_source": "https://mcpindex.ai/server/io-github-cappyeo-discord-mcp", "published_at": "2026-09-14 16:03:31+00:00", "updated_at": "2026-09-14 16:53:52.369371+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "ai-products"], "entities": ["Discord MCP", "mcpindex", "npm", "Claude", "Cursor", "Gemini CLI", "Cline", "Zed"], "alternates": {"html": "https://wpnews.pro/news/discord-mcp-io-github-cappyeo-discord-mcp-0-27-0", "markdown": "https://wpnews.pro/news/discord-mcp-io-github-cappyeo-discord-mcp-0-27-0.md", "text": "https://wpnews.pro/news/discord-mcp-io-github-cappyeo-discord-mcp-0-27-0.txt", "jsonld": "https://wpnews.pro/news/discord-mcp-io-github-cappyeo-discord-mcp-0-27-0.jsonld"}}