Connects Claude to RealEvents.co for creating and managing event pages entirely through conversation. You get six tools: browse public events, fetch event details by slug, create new event pages, register attendees, and manage existing events with update capabilities. Events are created without requiring an account, and each creation returns a manage token that you can either pass per-call or set as an environment variable for ongoing management. The server is published with npm provenance, so every version traces back to its exact GitHub commit and workflow run. Useful when you're coordinating events and want to handle registration pages without leaving your chat interface.
Create and manage events on RealEvents from any MCP-compatible AI assistant.
Documentation and install snippets: https://realevents.co/mcp
{
"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.
| Tool | Description |
|---|---|
list_public_events | Browse upcoming public events |
get_event | Get details of an event by slug |
create_event | Create a new event page |
register_for_event | Register an attendee |
get_manage_event | View an event's details and registrations (requires manage_token) |
update_event | Update event details (requires 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"
}
}
}
}
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.
Before publishing a new version:
version in package.jsonmcpName: "io.github.ykastelnik/realevents" is still presentversion and packages[0].version in server.json to matchvX.Y.Z and push: the publish.yml workflow handles the npm publish./mcp-publisher publish to sync the MCP Registry listingMIT