The inspection tools are what set this apart from a message-sending bot: list_target_accessible_channels and list_target_inaccessible_channels answer "why can this member not see that channel" directly, which is normally an afternoon of clicking through overwrites. Everything here acts on a live guild, so the bot's own role position decides how much of it works.
A Discord administration server built on discord.py, holding a bot session per token. The tools cover the structural side of a guild: channels and categories, roles, and the permission overwrites between them, plus the inspection tools that answer what a given role or member can actually see.
- Channels created in any type — text, voice, news, stage, forum, media or category — then edited, moved between categories, reordered by position, or deleted
- Channels listed for a guild, and any one of them fetched
- Roles created, edited including position, assigned to and removed from members, and deleted
- Permissions set or removed on a channel, set on a category, and set on a role
- Permission inspection from the other direction: what a role or member effectively holds, and what a given channel grants them
- The channels a target can reach, and the ones they cannot, listed separately
- Messages sent to a channel
Uv on your PATH, and a Discord bot token — the client passes it as the Authorization header, and each token gets its own session. The server binds to localhost by default, so nothing is exposed off the machine unless you change it.
One command — npx -y discord-mcp