Home/ Features/ RSVPingo for AI
RSVPingo for AI · MCP

Run your events from
Claude or ChatGPT.

RSVPingo speaks MCP — the Model Context Protocol. Connect your AI assistant once and create events, import guests, send invites, set reminders, and pull live analytics with plain English. No new dashboard to learn.

Claude · ChatGPT · Cursor OAuth + scoped keys Read-only mode available
Claude · rsvpingo MCPConnected
Create a Berlin summit event for Nov 14, invite the VIP list from HubSpot, and send a reminder 3 days before.
Created event “Berlin Summit · Nov 14”
Imported 142 guests from HubSpot VIP list
Scheduled reminder for Nov 11 · 9:00 AM
3 actions · 4.2s
Why this matters

Your AI assistant is now an event ops assistant.

The dashboard is still there if you want it. But for the work you do every week — bulk-importing a guest list, drafting an invite, checking who hasn’t replied, exporting a headcount — typing a sentence is faster than clicking through six screens.

MCP is an open standard from Anthropic. RSVPingo implements it natively, which means any AI client that speaks MCP (Claude desktop, Cursor, ChatGPT Apps, custom agents) can use the full RSVPingo API the moment you connect it.

42
MCP tools exposed — every API endpoint
3
supported clients out of the box
60s
to connect — OAuth handshake or API key
100%
scoped — per-key permissions you control
How it works

Connect once.
Run events in plain English.

Drop the RSVPingo MCP server into your AI client of choice. It auto-discovers every tool, prompt, and resource. From the next message on, your assistant can act on your account.

01 — Plug it in

One line in your MCP config.

RSVPingo runs a hosted MCP endpoint. Add it to Claude desktop, Cursor, or any MCP-compatible client by pasting one config block. OAuth handles the auth so you never paste a key into a chat.

  • Hosted MCP endpoint — no server to run yourself
  • OAuth flow for desktop clients, scoped API keys for headless
  • Auto-discovery — tools, prompts, and resources surface on connect
  • Per-workspace and per-event permission scopes
// claude-desktop.json
{
  “mcpServers”: {
    “rsvpingo”: {
      “url”: “https://mcp.rsvpingo.com”,
      “auth”: “oauth”
    }
  }
}
02 — Talk to it

No commands. Just ask.

Your assistant sees the full RSVPingo tool catalogue — create events, list guests, send invitations, query RSVPs, set reminder cadences, pull analytics. You ask in English; the assistant translates to the right tool calls.

  • 42 tools covering every API endpoint
  • Prompts library for common workflows (import + invite + remind)
  • Read-only resources for guest lists, analytics, and templates
  • Streaming responses for long-running ops (bulk imports, reminders)
You
“How many VIPs haven’t responded yet?”
Claude
13 of 24 VIPs haven’t responded. The longest pending invite went to Maya Lee on Oct 28 — want me to send a personal nudge to all 13?
You
“Yes, with a softer tone.”
Claude
Sent. I’ll notify you if anyone replies in the next hour.
03 — Auditable, scoped, safe

Every action logged. Every scope yours.

Each MCP key has its own permission scope — read-only by default, write-enabled per workspace, event, or tool. Every action shows up in the audit log with the AI client name and a one-line explanation of what changed.

  • Read-only mode by default — explicit opt-in for writes
  • Per-scope keys: workspace, event, segment, or tool group
  • Full audit trail with client name, timestamp, and diff
  • Revoke or rotate keys instantly from your dashboard
Audit log · today
Claude sent reminders10:42
Cursor imported guests (812)10:28
Claude created event10:11
ChatGPT exported attendance CSV09:54
What people use it for

Workflows worth delegating.

A few real prompts from RSVPingo users running events through Claude and ChatGPT.

📋
Bulk import & segment

“Pull last year’s gala list from Notion, dedupe against this year’s invites, tag the new VIPs.”

Draft invitations

“Write a 3-step reminder cadence in our brand voice for the Berlin summit, ending Friday.”

📊
Daily standup brief

“Each morning, summarise RSVP movement across all live events and flag anything off-pace.”

🎯
Targeted nudges

“Find guests who opened but didn’t RSVP, and send a personalised follow-up from the host.”

📦
Day-of exports

“Export today’s confirmed list with dietary, table assignment, and arrival window for catering.”

🧠
Post-event recap

“Write a one-pager on this event: attendance vs forecast, top channels, top no-show segment.”

“I run the entire month-of workflow from Claude now. Imports, reminders, exports — I haven’t opened the RSVPingo dashboard in two weeks. The dashboard is still there if I want it. I just don’t need to.”

SK
Sara Klein
Event Producer, Spark Studio
FAQ

MCP, answered.

What is MCP exactly?
MCP is the Model Context Protocol — an open standard from Anthropic that lets AI assistants connect to tools and data sources. Think of it as a USB-C port for AI: any MCP-compatible client (Claude desktop, Cursor, ChatGPT, custom agents) can plug into any MCP server. RSVPingo runs an MCP server, so any of those assistants can use your account.
Which AI clients work with this?
Out of the box: Claude desktop, Cursor, and ChatGPT (via MCP Apps). Any client that implements the MCP spec works — that includes custom agents built on the Anthropic, OpenAI, or other agent SDKs.
Can the AI accidentally send things I didn’t approve?
By default, every write action (sending invites, creating events, deleting guests) requires an explicit confirmation step in the chat. You can opt specific actions into auto-approve per workspace if you want a smoother flow.
How are my MCP keys secured?
Desktop clients use OAuth — your AI client never sees a raw key, and we can revoke a session in one click. Headless clients use scoped API keys: read-only by default, with per-workspace and per-tool-group permissions. All MCP traffic is encrypted in transit and the audit log shows every action.
Does this cost extra?
No. MCP access is included on every Pro and Enterprise plan at no additional cost. The free Starter plan includes read-only MCP access for trying it out.
Is this just for techies?
No. Setup is a single config block — copy, paste, OAuth, done. After that you’re just chatting with an assistant that happens to have your event tools. No code, no API knowledge, no Zapier-style wiring.

Plug RSVPingo into
your favourite assistant.

Free read-only MCP access on every plan. Full write access on Pro and above. Set up in under 60 seconds.

Compatible with Claude desktop, Cursor, ChatGPT, and any MCP-compliant client

Scroll to Top