---
name: fevori
description: Plan a party with Fevori - create the event, build the guest list, send personal email invitations and track who's coming. Use when a person wants to invite people to an event and collect RSVPs.
---

# Fevori

Fevori sends each guest a personal invitation by email, shows who has opened it, and keeps every RSVP in one guest list.

## Connect

- **MCP (preferred):** add the remote server https://fevori.app/mcp. It uses OAuth: your person signs in with Google and chooses what you may do. Tools: `whoami`, `list_events`, `get_event`, `create_event`, `update_event`, `delete_event`, `list_guests`, `get_guest`, `add_guests`, `update_guest`, `remove_guest`, `send_invitations`.
- **REST:** https://fevori.app/api/v1, described by https://fevori.app/api/v1/openapi.json.
- **No access yet:** see https://fevori.app/auth.md. You can register an agent account yourself and give your person a claim link.

## Plan an event

1. Ask for what you don't know: title, date and time, time zone, place, and anything guests should know.
2. Create the event. It starts as a draft, so nothing is visible to anyone.
   - Times are ISO 8601 **with a UTC offset** (`2026-06-06T19:00:00-07:00`); also set `timezone` (IANA, e.g. `America/Los_Angeles`) so guests see local times.
   - Optional: `capacity` (most people who can say yes), `visibility: "public"` for a page anyone can RSVP on.
3. Add guests: name, email (needed for invitations), phone, and `max_party_size` if they may bring others. Emails must be unique within an event; duplicates come back as failures, not errors for the whole batch.
4. Show your person the event and guest list, and confirm before going further.
5. Publish (`status: "published"`). Invite links only work once published.
6. Send invitations, **only after your person confirms the guest list and any personal message**. Without guest ids, it emails every guest with an address who hasn't been emailed yet. It sends real email in their name and can't be undone.

## Follow up

- `list_guests` with `status`: `yes`, `maybe`, `no` for replies; `viewed` (opened the invitation), `opened` (opened the email), `pending` (sent), `unsent`; `bounced`, `failed` or `unsubscribed` when it couldn't reach them.
- Each event's `counts.attending` is how many people are coming, counting whole parties.

## Rules

- Never send without confirmation. Never invent guests or email addresses.
- Texts are sent only from the event page by the person, who confirms each guest agreed to get them.
- If you get `account_unclaimed`, give your person the `claim_url` and wait for them to claim the account.