Choose your path

Start from the outcome you need. The paths below preserve the same owner-managed custody and exact-scope model, but they avoid making every reader traverse the complete reference.

I want the first verified readCreate the bot, generate the minimum grant, validate the policy, prove stdio startup, and copy one read request.

I am switching from another Discord MCPGenerate a release-exact outcome map, review every trust-model change, and stage a verified cutover without importing source policy.

I need to decide whether it fitsReview custody, privacy, approval, deployment, and compatibility boundaries before installation.

I need the privacy contractReview exact credential, Discord-data, local-record, observability, control, and deletion behavior.

I need to compare alternativesReview a dated source-audited matrix with published criteria, direct evidence, and explicit audit limits.

I want a guided product tourFollow the release-exact operator journey before creating a bot or granting Discord access.

I need host configurationImport the verified one-click bundle or generate one credential-free activation digest with exact host adapters.

I want more read coverageAdd one bounded recipe or policy scope after the read-only baseline works.

I need a reviewed writeUnderstand the plan, approval, freshness, coordination, execution, readback, and receipt sequence first.

The host cannot initializeCompare the launch contract field by field, then separate policy, credential, Discord, stdio, and host failures.

I need the exact contractSearch the release's tools, schemas, annotations, prompts, resources, completion routes, and digests without credentials.

I need release evidenceVerify package identity, provenance, inventories, signatures, image evidence, and their explicit limits.

I want to contributeReview security boundaries, capability design expectations, tests, and reporting routes.

Keep the first success read-only

Do not use a write as a connectivity test. A successful read proves identity, policy, Discord access, process launch, MCP negotiation, and response handling without creating Discord state.