organize-discord

name	organize-discord
description	Organize the user's Discord servers into sidebar folders. Use when the user asks to clean up, group, sort, or categorize their Discord server list, or mentions their Discord sidebar being messy.

Organize Discord servers

This project exposes Discord folder management as an MCP server (discord-organizer) plus a CLI fallback. You categorize the servers using your own reasoning — there is no LLM inside the code.

When to use

User says things like: "organize my discord", "my server list is a mess", "group my discord servers", "sort my discord sidebar", "clean up discord folders".

Prerequisites check

1. .env file exists and contains DISCORD_TOKEN. If not, ask the user to copy .env.example → .env and fill it in (token grab instructions in AGENTS.md).
2. The MCP server discord-organizer is connected. If tools aren't available, the user may need to restart Claude Code so .mcp.json is loaded.

Workflow (MCP — preferred)

1. Discover. Call list_guilds to see what the user has. Also call read_folders to see the current layout — don't overwrite a layout you didn't first read.
2. Propose. Look at the guild names and group them into 5–12 short, clear folders (Gaming / Dev / AI / Communities / etc. — adjust to what's actually there). Show the proposed grouping to the user as a readable list and ask for confirmation or tweaks before mutating anything. Respect any preferences the user mentions ("keep crypto separate", "no NSFW folder", etc.).
3. Dry-run. Call apply_folders with dry_run: true to surface the exact diff. Report folder count and named-folder count to the user.
4. Apply. On user approval, call apply_folders with dry_run: false. The server auto-backs up before mutating and returns the backup path — pass it on to the user so they know rollback is available.
5. Rollback path. If the user dislikes the result, call restore_folders with the auto-backup path.

Hard rules

• Never call apply_folders (non-dry-run) without explicit user approval of the proposed grouping. This mutates the user's main account.
• Always present the proposed folders to the user as a list before applying — don't surprise them with a layout they haven't seen.
• Don't loop or batch. This is a one-shot operation per request.
• Treat DISCORD_TOKEN as a password. Don't echo it, don't paste it elsewhere.

CLI fallback (if MCP isn't available)

The same operations are exposed as bun run list / backup / apply / restore. To use the CLI flow, write a plan.json in the shape documented in AGENTS.md then run bun run apply --dry-run followed by bun run apply. Slower (each command re-logs into Discord) but works in any agent with a bash tool.

See AGENTS.md for full file shapes and command reference.