evite-mcp
MCP server for Evite — read and act on your events as both guest (invitations received) and host (events you created): list events, view guest lists & RSVP tallies, RSVP, message guests, and create/edit events.
Setup
Option A — Claude Code (direct MCP)
Add to .mcp.json in your project or ~/.claude/mcp.json:
{
"mcpServers": {
"evite": {
"command": "npx",
"args": ["-y", "evite-mcp"],
"env": {
"EVITE_EMAIL": "you@example.com",
"EVITE_PASSWORD": "yourpassword"
}
}
}
}
Option B — global install
npm install -g evite-mcp
Auth
The server resolves a session in priority order (see the README for details):
EVITE_EMAIL + EVITE_PASSWORD — headless email/password login (preferred).EVITE_SESSION_COOKIE — a raw cookie: header copied from a signed-in evite.com tab.- Fetchproxy bootstrap — lifts session cookies from a signed-in evite.com browser tab. Opt out with
EVITE_DISABLE_FETCHPROXY=1.
Read (6 + healthcheck): evite_list_events, evite_get_event, evite_list_guests, evite_rsvp_summary, evite_list_messages, evite_list_templates, evite_healthcheck.
Write (confirm-gated): evite_rsvp, evite_send_message, evite_broadcast, evite_create_event, evite_update_event, evite_add_guest, evite_update_guest, evite_remove_guest, evite_send, evite_cancel_event, evite_reinstate_event, evite_duplicate_event.
Every write tool takes confirm: boolean. Without confirm: true it makes no network call and returns a dry-run preview of exactly what would be sent — the safe default. The authoring flow is evite_create_event → evite_add_guest → evite_send.