Realevents

io.github.ykastelnikPublished by GitHub account ykastelnikv1.4.0Updated Oct 26, 2026

Create and manage events in seconds from your AI assistant. No account needed.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant create and manage RealEvents event pages, RSVP guests, and read organizer stats and guest comments.

What you can do
  • Browse and read public events, filtering by format, date range or search term and fetching details by slug
  • RSVP for an attendee as going, maybe or not going, with plus-ones and a note
  • Create event pages and get back the public link and manage link
  • Manage events with a manage token: edit details, duplicate, cancel, set a cover image from a public URL
  • Read the guest list, head-count, page views and view-to-attendance stats
  • Read and post comments on the guest thread when the organizer has enabled them
When to use it
Useful when you want an assistant to publish an event page, collect RSVPs, or check attendance and guest questions without opening the RealEvents site. Public browsing and RSVP need no token; organizer work needs the manage token.
Requirements
Runs locally via npx (Node.js) as a stdio server; desktop clients only. No account or API key is needed for public tools. Organizer tools need a manage token, returned by create_event and optionally supplied through the REALEVENTS_MANAGE_TOKEN environment variable.
Before you install
The manage token is the only way to manage an event later, so it must be saved and kept private; storing it in REALEVENTS_MANAGE_TOKEN puts it in the client config. Organizer tools change live event data: updates, cancellation, cover changes and comments visible to every guest who RSVPed. Cover images must be public URLs, so the image is fetched from a third party.

Installation

In SourceWeft

  1. Open Realevents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

RealEvents MCP Server

Create and manage events on RealEvents from any MCP-compatible AI assistant.

[CI] [CodeQL] [npm version] [npm downloads] [License: MIT]

Documentation and install snippets: https://realevents.co/mcp

Install

json
{  "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.

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:

ToolDescription
list_public_eventsBrowse upcoming public events. Filter by format, date range or search term.
get_eventGet an event's public details by slug. Follows old links after a slug change.
register_for_eventRSVP for an attendee: going, maybe or not going, with plus-ones and a note.
create_eventCreate a new event page. Returns the public link and the manage link.

Organizer tools, all requiring the manage token:

ToolDescription
get_manage_eventFull event details plus the guest list.
list_registrationsThe guest list on its own, optionally filtered to confirmed / maybe / declined.
get_event_statsPage views, head-count, remaining capacity, view-to-attendance rate.
update_eventChange any event detail or setting.
duplicate_eventCopy the event into a new draft one week later.
cancel_eventMark the event cancelled. The page stays online.
set_coverSet the cover image from a public image URL.
list_commentsRead the guest conversation: questions, replies and reactions.
post_commentPost 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:

json
{  "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:

  1. Bump version in package.json
  2. Verify mcpName: "io.github.ykastelnik/realevents" is still present
  3. Bump version and packages[0].version in server.json to match
  4. Tag vX.Y.Z and push: the publish.yml workflow handles the npm publish
  5. Locally: ./mcp-publisher publish to sync the MCP Registry listing

License

MIT

Source: README.md at commit 33e2daf

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.4.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts