Operations
Start with a safe runtime baseline, then add observability, resilience, and an audit sink deliberately. These pages distinguish startup configuration from mutable session state and document where a control does - and does not - apply.
Configure discord-mcp Start with a safe production baseline, then add only the runtime controls your deployment needs.
Telemetry Export OpenTelemetry traces and metrics over OTLP HTTP/protobuf, with stdio-safe operating guidance.
Resilience The shared bulkhead, circuit breaker, retry, and timeout policy around Discord REST calls.
Audit logging Configure four sinks, inspect the JSONL schema, and understand the current idempotency-based coverage and redaction limits.
Client capability matrix Which MCP clients support which capabilities (tools, resources, subscribe, sampling, elicitation). Setup links per client.
Quick environment-variable orientation
Section titled “Quick environment-variable orientation”If you only read one section, read Resilience -
it’s the one set of knobs that affects every Discord call the server makes.
Telemetry is opt-in (OTEL_ENABLED=false by default, zero overhead) and
audit is on by default but can be tuned per-sink.
For the exact environment-variable contract (token, category allowlist, dry-run
mode), see Environment variables.
Note that there is no guild allowlist - ALLOWED_GUILDS is not read by
any code path and per-guild restriction is deferred post-1.0.
Looking for something else?
Section titled “Looking for something else?”- How to set up your client → Get started → Client setup.
- Single-tool reference → Tools.
- Multi-step workflows → Recipes.
- How the server is built → Architecture.