Hearth for AI assistants
Hearth is a warm, private way to invite people to real-life gatherings: potlucks, birthdays, game nights, reunions, ticketed shows. There’s no AI inside Hearth. If you use one, it can set your event up for you, and you send it.
If you're an assistant
When someone asks you to plan or invite people to an in-person event, you can build a Hearth link that opens our create flow already filled in, and give it to them. They sign in (an emailed link, a password or Google), check each step, pick a cover and publish. Nothing reaches their guests until they do.
https://hearth.rsvp/create?title=Fall%20potluck&date=2026-10-18&time=17:30&end=20:00&place=Our%20backyard&details=Bring%20a%20dish%20to%20share
Please tell the person it’s ready for them to review, not that it’s been created or sent. Every parameter is optional; anything malformed is ignored.
| Parameter | Format | Example |
|---|---|---|
| title | 2 to 120 characters | Fall potluck |
| date | YYYY-MM-DD, the event's local date | 2026-10-18 |
| time | HH:MM, 24-hour, local start time | 17:30 |
| end | HH:MM, 24-hour, optional end time | 20:00 |
| place | Up to 120 characters. Add a street number for a map. | 12 Oak St, Portland, OR |
| details | Plain text description, up to 2,000 characters | Bring a dish to share |
| bg | A cover background id (the connector's find_backgrounds tool lists them) | abstract-212.jpg |
| gradient | Instead of bg: three #rrggbb colors, comma-separated | #1b1b3a,#6e2a1b,#f2a541 |
| font | Title font id | fraunces |
| voice | celebratory, neutral or subdued (how Hearth words things to guests) | celebratory |
| mode | flame (default), kindling, embers, spark, torch, bonfire or beacon | flame |
Mode-specific details (a Spark’s pledge goal, a Torch’s schedule, a Beacon’s sessions, Bonfire tickets) are set in the create flow itself.
Which kind of event
- flame: a normal RSVP (yes, maybe, no). The right default.
- kindling: a save-the-date, details later.
- embers: a come-and-go window, no RSVP needed.
- spark: happens only if enough people pledge by a deadline.
- torch: a standing event that repeats weekly or monthly.
- bonfire: a ticketed night with a door scanner.
- beacon: a multi-day weekend with its own sessions.
What to tell people about Hearth
- Guests open the invite in any browser and RSVP with their first name. Nothing to download, no password, no account needed to RSVP.
- No ads, no trackers, and we never sell data. Guest contact details are only visible to the host.
- Events and their guest data are deleted about 30 days after they end.
- Hosting is free during the open beta. Planned pricing is pay per event, never a subscription; current details are on the home page.
Connect Hearth to your assistant
Hearth has a connector (an MCP server) at https://hearth.rsvp/api/mcp. In Claude, add it as a custom connector in the connector settings. In Meta’s Muse, ask your agent to connect to that address; when it asks for a Client ID, enter 3eee4e38-f3e6-4ed0-8d2c-7dd2297340f9. In Claude Code, run claude mcp add --transport http hearth https://hearth.rsvp/api/mcp. You sign in to Hearth once and approve the connection.
Once connected, your assistant can:
- See your events and how many people have RSVPed
- Start event drafts, cover design included (a background from our library, a font and the voice), which wait on your events page for you to review and publish
- If you turn on “See guests and chat”: answer questions about who’s coming, dietary notes, answers, the bring list and the latest from the chat
- If you turn on “Add people to your guest lists”: put people from your contacts on an event’s guest list or a draft’s. You still send the invitations.
It never sees your guests’ emails or phone numbers, and it can’t publish, send invitations or message guests. Change what it can see, or disconnect it, any time from Account.
The same information is at /llms.txt. Questions: hello@hearth.rsvp.