Operate GuildControl MCP

The operator CLI is designed as an evidence ladder. Each step isolates one boundary before the next one is introduced, so a failure has a useful category instead of becoming a generic startup error.

Establish the read-only baseline

1. Create an owner-managed Discord application and bot, then run npx guildctl and choose the MCP host first.

2. Review the exact server-observer grant, install it into one locked guild, and type that guild ID exactly.

3. Let the command verify the token's application, exact installation, strict non-secret policy, and real child-process stdio path.

4. Open the private selected-host guide, supply the host's protected credential, reload it, and complete the first channel inventory.

5. Use catalog, config validate, doctor, smoke, or the manual setup route only when you want independent evidence or need to isolate a failure.

The first verified read guide provides the shortest supported route. Use advanced manual setup and verification for release-pinned commands, independent evidence, alternate credential custody, and the complete recovery order.

Expand deliberately

Once the baseline works, add one outcome at a time:

Read and discoverySearch, bounded inventories, privacy-safe member and ban evidence, and thread or forum context.

Messages and interactionsReviewed thread, pin, crosspost, forwarding, poll, and private webhook workflows.

Guild lifecycleInvites, templates, onboarding, settings, Community, incidents, expressions, events, and stages.

Channels and rolesPermission evidence, exact metadata and ordering, additive creation, roles, blueprints, and resumable scaffolds.

Publishing and membersLocal-file and static message layouts, reactions, direct messages, deletion, member changes, moderation, and pruning.

Recipes add bounded authority

Use guildctl recipe enable to see and confirm one complete additive policy expansion in a single interactive flow. Detached recipe plan and recipe apply remain available for separate review. Neither path bypasses Discord permissions, widens exact scope implicitly, or makes an immediate write path available.

Recover and verify

• Use troubleshooting for setup, host initialization, policy, credential, Discord, and stdio failures
• Use release verification to distinguish provenance, inventories, signatures, and reproducibility from security claims they cannot make
• Use the exact contract explorer to inspect the callable release without a credential or Discord request