realevents-mcp
An MCP server for creating, browsing, registering for, and managing RealEvents event pages.
Create an event (
create_event) with title, start time, format, location, virtual link, description, max attendees and organizer email; returns the public link, manage link and slug (save the manage link — it's the only way to edit later).Browse public events (
list_public_events) filtered by format, date range (today/this_week/this_month), title search, and paginated up to 50 per page.Get one public event (
get_event) by slug — title, date, location, registration count, description.Register an attendee (
register_for_event) by slug and email, with optional first/last name; returns confirmation with status and event date.Read organizer details (
get_manage_event) — full event data plus the guest list, authenticated with a manage token orREALEVENTS_MANAGE_TOKEN.Update an event (
update_event) — change any field (title, slug/URL, theme, format, location, description, start/end time, virtual link, max attendees, listed, organizer email, notify-on-registration) or setstatustodraft,publishedorcancelled.
Note: the schema exposes only these 6 tools, so README-described capabilities (guest-list filtering, stats, duplicate, cancel tool, set_cover, comments) are absent here; create_event also takes no timezone, and register_for_event takes no status, plus-ones or note.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@realevents-mcp List public events happening next week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RealEvents MCP Server
Create and manage events on RealEvents from any MCP-compatible AI assistant.
Documentation and install snippets: https://realevents.co/mcp
Install
{
"mcpServers": {
"realevents": {
"command": "npx",
"args": ["-y", "realevents-mcp"]
}
}
}For Claude Desktop on macOS, the config file is at ~/Library/Application Support/Claude/claude_desktop_config.json. For other clients, see their MCP documentation.
Related MCP server: Google Calendar MCP Server
Agent skill
skills/realevents/SKILL.md teaches an assistant when
and how to use these tools: creating an event with the right timezone, handing back
the manage link, and the head-count and guest-list rules below. Copy the
skills/realevents folder into your client's skills directory (for Claude Code,
~/.claude/skills/) alongside the server config above.
Tools
Public, no token needed:
Tool | Description |
| Browse upcoming public events. Filter by format, date range or search term. |
| Get an event's public details by slug. Follows old links after a slug change. |
| RSVP for an attendee: going, maybe or not going, with plus-ones and a note. |
| Create a new event page. Returns the public link and the manage link. |
Organizer tools, all requiring the manage token:
Tool | Description |
| Full event details plus the guest list. |
| The guest list on its own, optionally filtered to confirmed / maybe / declined. |
| Page views, head-count, remaining capacity, view-to-attendance rate. |
| Change any event detail or setting. |
| Copy the event into a new draft one week later. |
| Mark the event cancelled. The page stays online. |
| Set the cover image from a public image URL. |
| Read the guest conversation: questions, replies and reactions. |
| Post to the thread as the organizer. Visible to every guest who RSVPed. |
Comments only work on events where the organizer has switched them on
(update_event with allow_comments: true). Until then both comment tools return
a message saying exactly that.
Cover images
set_cover takes a public image URL, not a file. MCP tool arguments are JSON
text, so an assistant cannot hand a local image to the server; if the picture is on
the user's computer, the manage page's upload does the job better anyway (drag and
drop, preview, crop). Around 1200px wide or more looks best - set_cover says so
when the image is smaller rather than silently accepting a thumbnail.
Timezones
create_event takes a timezone (an IANA name such as Europe/Paris) alongside
start_datetime. Set it. The start time is interpreted in that zone, and the
zone defaults to UTC, so creating an event for 19:00 without one produces a page
that reads 19:00 UTC: the wrong hour for everyone outside it.
Prefer a local time with no trailing Z:
start_datetime: "2026-06-15T19:00:00"
timezone: "Europe/Paris"Attendance is counted in people
An event's attendance figure is a head-count: confirmed guests plus everyone they bring. A guest arriving with three others takes four of the available places, so a party can be refused on an event that still shows free rows. When that happens the error states how many places are left, so the call can be retried with a smaller party rather than reported as a failure.
Plus-ones only attach to a confirmed answer, and are capped by the event's own
plus_ones_limit (0 disables them). When the organizer collects names rather than
a headcount, every declared guest needs one. get_event reports both settings.
Manage token
Events created with create_event return a manage_token. Save it: it is the only
way to manage the event later.
To set a default token so you don't have to pass it on every call:
{
"mcpServers": {
"realevents": {
"command": "npx",
"args": ["-y", "realevents-mcp"],
"env": {
"REALEVENTS_MANAGE_TOKEN": "your-token"
}
}
}
}Security
Signed with npm Provenance, built from this repository via GitHub Actions. Every published version is traceable back to the exact commit and workflow run that built it.
Links
For maintainers: publishing checklist
Before publishing a new version:
Bump
versioninpackage.jsonVerify
mcpName: "io.github.ykastelnik/realevents"is still presentBump
versionandpackages[0].versioninserver.jsonto matchTag
vX.Y.Zand push: thepublish.ymlworkflow handles the npm publishLocally:
./mcp-publisher publishto sync the MCP Registry listing
License
MIT
Available Tools
6 toolscreate_eventA
Creates an event page on RealEvents. The event is created with a start time only. To set an end time, duration, or to update other details (description, location, theme, cover image), use the update_event tool with the manage_token returned by this tool. Returns the public link, manage link, and slug. Save the manage link - it is the only way to edit the event later.
Inputs: title (required), start_datetime (required), format, location, +4 more.
get_eventA
Get details of a public event by its slug. Returns title, date, location, registration count, and description.
Inputs: slug (required).
get_manage_eventA
Get full event details including the registrations list. Requires the manage token (the secret part of the manage URL) or REALEVENTS_MANAGE_TOKEN env var.
Inputs: manage_token.
list_public_eventsA
Browse upcoming public events on RealEvents. Filter by format, date range, or search term. Returns titles, dates, locations, and public links.
Inputs: date, page, format, search, +1 more.
register_for_eventB
Register an attendee for a public event by slug. Returns confirmation with status and event date.
Inputs: slug (required), email (required), last_name, first_name.
update_eventB
Update an existing event by manage token. Only provide the fields you want to change. Use this to set end_datetime, change status (e.g. 'cancelled'), or update any other detail after creation.
Inputs: slug, theme, title, format, +11 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: create, read public/private, list, register, update. No overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_event, get_event, list_public_events), making them predictable and easy to distinguish.
With 6 tools, the set covers core event management operations without being overwhelming or sparse. Perfectly scoped for the domain.
Covers creation, reading (public and private), listing, registration, and updating. The only minor gap is the lack of a dedicated delete tool, but cancellation via update_event mitigates this.
Maintenance
Related MCP Connectors
Enables AI assistants to retrieve event data and execute event management operations in Nunify.
Manage Eventtia events, attendees, registrations, agendas and check-ins from any AI assistant.
Run in-person events from your AI: create events, manage tickets, attendees, broadcasts.
Run ticketed events from your AI assistant: create events, sell tickets via Stripe, check in.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to search, filter, and analyze Microsoft events (conferences, workshops, webinars) using the Microsoft Events API.42MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates Google Calendar with AI assistants via MCP, enabling calendar listing and event CRUD operations.-
- FlicenseNot gradedqualityDmaintenanceExposes Cal.com scheduling tools to AI agents via MCP, enabling listing event types, checking availability, and managing bookings (create, cancel, reschedule).-
- AlicenseNot gradedqualityDmaintenanceMCP server for eventos event management platform, enabling AI assistants to manage events and tickets via API integration. Supports authentication, ticket CRUD operations, and listing with pagination.1MIT