Discord
Safety-first MCP server for Discord with privacy-safe reads, audits, and reviewed administration
- Transport
- Not stated
- Package
- —
- Registry id
- app.lasers.guildcontrol/discord
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
GuildControl MCP is a local stdio connector for a Discord bot you create, install, and control. It combines broad typed Discord coverage with a strict non-secret policy, bounded privacy-aware results, reviewed writes, and content-free operational evidence. Interactive approval is required for mutating operations, which prepare keyed evidence, replan, coordinate durably, and read back outcomes where Discord permits.
The connector does not operate a shared bot, hosted relay, or token store, keeping the token in a caller-owned secret source. Discord activity records preserve identifiers, hashes, timestamps, and outcomes but exclude message content, names, URLs, embeds, or profiles. Write workflows are disabled until a user deliberately adds one, requiring a fail-closed flow through installation and verification.
The tool is self-hosted local software, not a managed service, and remains subject to real Discord platform constraints. Users can import a deterministic MCPB or generate digest-bound host projections without placing credentials in static configuration.
Summary drafted from the project's own website. Every sentence is backed by text on that page and was reviewed before publishing.