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. Inspect the credential-free catalog and recommended read-only preset.

2. Generate the exact Discord bot installation plan without opening a browser or requiring a token.

3. Create one strict non-secret policy while delivering the token only through a caller-owned secret source.

4. Run offline validation, then online doctor, then the real stdio smoke test.

5. Import the verified MCPB when the host and credential policy support it, or generate the private host activation guide and merge only one exact adapter projection.

6. Complete the first structured channel inventory through the host.

The first verified read guide provides the exact release-pinned commands, success criteria, and 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

A recipe plans and applies one reviewed policy expansion. It does not bypass Discord permissions, widen exact scope implicitly, or make 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