pulsemcp verified Safe content atomic mcp-remote

Discord

Discord MCP server that provides AI assistants with comprehensive Discord bot capabilities through a route-generated tool system and real-time Gateway events. The implementation features a catalog-driven approach where Discord API endpoints are automatically converted into MCP tools, organized into modular packs (CORE, ADMIN, MEDIA, COMMUNITY, DEVTOOLS) that can be selectively enabled, with built-in security through allow-lists for guilds/channels, human-in-the-loop confirmations for destructive operations, and sanitized mention handling. It supports both REST API operations for standard Discord actions like messaging, role management, and channel administration, plus Gateway integration for real-time event streaming with configurable filters, making it valuable for building Discord moderation bots, community management tools, and AI assistants that need to interact with Discord servers while maintaining security boundaries.

Cognium trust score

96%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: communication
Source: PulseMCP
Repository: github.com/bennettschwartz/discord-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Discord from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"