domain: discord.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate as a bot with the Manage Events permission in the target guild.
Create an event with POST /guilds/{guild.id}/scheduled-events, choosing entity_type (STAGE_INSTANCE, VOICE, or EXTERNAL), which determines whether channel_id, entity_metadata, or scheduled_end_time are required.
For EXTERNAL (in-person/off-Discord) events, supply entity_metadata.location and an explicit scheduled_end_time, since Discord can't infer an end time without a voice/stage channel.
Manage lifecycle status (scheduled -> active -> completed, or cancelled) via GET/PATCH on /guilds/{guild.id}/scheduled-events(/{event.id}).
Read interested-user/RSVP counts via the event's subscribed-users endpoint; the creating account is auto-subscribed.
Known gotchas
A guild can have at most 100 events in SCHEDULED or ACTIVE status simultaneously — high-volume church calendars may need to prune/complete old events.
Required fields differ by entity_type — sending voice-channel fields for an EXTERNAL event (or vice versa) causes validation errors.
Creating/updating events fires gateway events (not just REST responses) — a webhook-only integration will miss real-time updates without a gateway connection.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?