Environment variable reference

This is the complete runtime contract for discord-mcp. Every setting is read when the relevant transport starts; invalid schema-backed values make serve exit with a precise error and are reported by discord-mcp doctor.

For deployment decisions and a safe starting point, see Configure discord-mcp.

Note

Most booleans accept 1, true, or yes as truthy. Default-on controls use different semantics: only the literal string false turns them off.

Browse by concern

Access and scopeCredentials, guild boundary, category authorization, and progressive tool discovery.

SafetyThe dry-run gate that protects confirmation-gated tools.

RuntimeGateway subscriptions and server logging.

ObservabilityOpenTelemetry service, exporter, and sampling controls.

ResilienceRetry, timeout, circuit-breaker, and concurrency settings.

Audit loggingMutation audit switch, sink, and file path.

Source and validation

Most variables are defined in the Zod schema. The exception is MCP_DRY_RUN: the confirmation precondition reads it directly from process.env, so doctor cannot validate it.