Party RSVP
Create invitation

Works with Claude & ChatGPT

First of its kindBuilt for AI agents

The first invitation app your AI can run

Connect Party RSVP once and your assistant builds the party from a sentence, fixes the details, loads the guest list — then answers from your real RSVP state: who is coming, who went quiet, what nobody has offered to bring. No exporting, no pasting a guest list into a chat window.

Your assistantClaude · ChatGPT · any MCP client

What still needs buying for Saturday?

called get_food_list

Still openIce (0 of 1) and paper cups (0 of 1). Nobody has claimed either.

CoveredTwo hot mains, three sides, a salad and the drinks cooler.

Worth a lookThe Nguyens claimed the dessert, then replied can't make it.

Live

MCP connector

A remote MCP server at partyrsvp.app/api/mcp — the standard Claude and ChatGPT both speak.

Live

Agent keys

Per-account keys you create and revoke on this page’s in-app twin. Hashed at rest, shown once, three max.

Live

CLI

One dependency-free script: partyrsvp events, summary, food — same key, same endpoint.

Live

Agent-readable pages

llms.txt for answer engines, and every invitation has a markdown twin at /i/<slug>.md.

Live

Drafting tools

Your assistant can create a draft event, edit details and add guests. Publishing and every send stay buttons only you can press.

Planned

Send tools

Sending nudges and messages from your assistant — behind an explicit per-send confirmation step.

What your assistant can do today

Four tools read, three draft. Your assistant can stand up an event from a sentence, fix a time or add the guest list — but nothing it can reach publishes, sends, or sees a guest’s contact details. Every outward-facing move stays a button only you can press.

list_events

Your events with reply counts at a glance

get_event

One event in full — guests, statuses, links

get_rsvp_summary

The same briefing we email you: headcount, notes, watch-outs

get_food_list

The bring list — what's claimed, what's still open

create_event

Draft a new event from your description — you review and publish

update_event

Fix a detail: time, place, invitation text, capacity

add_guests

Type in the guest list, names with optional contacts

Connect it

One endpoint for every client: https://partyrsvp.app/api/mcp — transport Streamable HTTP. Whatever the app calls it, you’re adding a remote MCP server, never a local command.

1 · Create an agent key

On the Connect your AI page (Account menu), tap Create key and copy it — it’s shown once. Revoking it there disconnects every assistant using it, instantly.

2 · Claude (claude.ai & desktop)

  1. Settings → Connectors → Add custom connector
  2. URL: https://partyrsvp.app/api/mcp
  3. Tap Connect — our approval page opens; paste your prsvp_… key there
  4. Ask: “List my events and tell me who hasn’t replied.”

3 · ChatGPT

ChatGPT has two different settings screens depending on where you are — find yours:

On chatgpt.com (web) — connectors added here appear in the apps too:

  1. Settings → Apps & Connectors → enable Developer mode (under Advanced) if you haven’t
  2. Create → connector type MCP server, URL https://partyrsvp.app/api/mcp
  3. Authentication: OAuth — ChatGPT opens our approval page; paste your key there
  4. In a chat, add the connector from the composer’s tools menu and ask away

In the desktop app, if Settings shows Plugins with an MCPs tab:

  1. Plugins → MCPs → Add → Connect to a custom MCP
  2. Name: PartyRSVP, Type: Streamable HTTP — the “Command to launch” box becomes a URL field
  3. URL: https://partyrsvp.app/api/mcp — leave Arguments and Environment variables empty; your key never goes there
  4. Save, switch the server on in the list, and restart if it doesn’t appear. When it asks to authenticate, our approval page opens — paste your key; if it offers custom headers instead, add Authorization: Bearer prsvp_…

4 · Desktop apps with an “MCPs” screen

Some clients show a form with Type: STDIO / Streamable HTTP, a “Command to launch”, and an Arguments list. Three rules:

  1. Type: Streamable HTTP — never STDIO. STDIO is for local programs; ours is a URL.
  2. The URL goes in the URL field that appears: https://partyrsvp.app/api/mcp
  3. Never put your key in Arguments. If the app supports OAuth it will open our approval page; if it offers custom headers instead, add Authorization: Bearer prsvp_…

5 · Claude Code

claude mcp add --transport http partyrsvp https://partyrsvp.app/api/mcp \
  --header "Authorization: Bearer prsvp_YOUR_KEY"

6 · Terminal, if that’s your thing

curl -fsSL https://partyrsvp.app/cli.sh -o /usr/local/bin/partyrsvp
chmod +x /usr/local/bin/partyrsvp
partyrsvp login     # paste your agent key
partyrsvp events    # also: event <id> · summary <id> · food <id>

If it doesn’t connect

  • “Command to launch” asking for a program? The type is set to STDIO — switch it to Streamable HTTP.
  • “Couldn’t register” errors are stale — we speak OAuth now; try Connect again.
  • 401 means the key: it starts with prsvp_, and it may have been revoked.
  • Keys pasted into screenshots or shared chats should be revoked and re-created.

The fine print, plainly

Agent access is scoped to your account. Keys are stored as hashes and never shown twice. Guest email addresses and phone numbers are never in any agent response. Writes stop at drafting: an agent-created event stays private until you publish it, and no tool can send anything — your assistant will never text your guests on a whim. When send tools arrive, each send will need your explicit confirmation.

Create a free account