The RSVPify MCP is a Model Context Protocol server that connects your live RSVPify workspace to an AI assistant. MCP is an open standard that lets assistants like Claude and ChatGPT read data and take actions in outside tools. With RSVPify's, you can build events, manage guests, send campaigns and pull reports by describing what you want in plain language.

RSVPify's MCP works with any MCP-ready assistant, including Claude, ChatGPT, Cursor and tools your team builds in-house. You connect RSVPify once as a connector in the assistant you already use, then work with your event data in that conversation. There is no separate RSVPify chat window to learn and no switching between tabs.

Add RSVPify as a connector in your AI assistant and sign in with your RSVPify workspace credentials. Setup takes a few minutes and requires no code, no developer and no separate API key work. Your session inherits the role and permissions your RSVPify account already has, so you see exactly what you would see in the app.

RSVPify Cue is the assistant built into your RSVPify workspace, ready to use with no setup. The RSVPify MCP brings those same capabilities into the AI assistant you already use, such as Claude or ChatGPT. Every action Cue can take is available through the MCP. Choose Cue to work inside RSVPify, choose the MCP to work alongside your other tools.

It builds both. Describe the event and RSVPify creates a working registration form and a branded event website, not a copy suggestion. You can point it at a URL and have it pull your brand styling, specify the questions the form should ask, and set the registration flow. Everything arrives as a draft for you to review before it goes live.

Yes. You can import a guest list, tag segments such as VIPs or sponsors, assign seating, update RSVPs and pull check-in status, all by describing what you need. For example, importing a 240-person CSV, tagging one company's executives as VIP and seating them at the head table is a single request.

Yes. You can draft and send multi-touch email campaigns in your brand voice, target them by segment such as everyone who registered in the last 48 hours, attach files, and schedule reminders and follow-ups. Because RSVPify already connects to Slack, Gmail, Salesforce, HubSpot and Notion, campaign work and handoffs stay in the systems your team uses.

You can analyze anything collected at registration, including ticket sales, attendance, check-in data, guest responses, donations and meal preferences, across one event or your whole workspace. Ask for a post-event wrap-up covering attendance, revenue, dietary requirements and top registration questions, and you get a finished report exported to PDF, XLSX or CSV.

Yes. You can pull revenue, registration, attendance and no-show figures for a single event or compare them across a series, then layer in what guests told you at registration. That gives you the inputs for cost per attendee, revenue per registrant and year over year comparisons without exporting to a spreadsheet first.

No RSVPify data is used to train foundation models, and that holds for every model provider. RSVPify is SOC 2 Type II certified and aligned with GDPR and CCPA. Workspace admins can flip a PII switch that runs AI on aggregates only, with no access to guest personal data, and every AI action is audit-logged exactly like a human user's.

No. Nothing publishes, sends or goes live until a person approves it. AI sessions inherit the role and permissions of the RSVPify account behind them, so an assistant can never reach an event or a field that the account could not already reach. Every action is logged and attributable, and admins can revoke access at any time.

A general chatbot can draft a run of show. It cannot see who registered. RSVPify works against your live event data and takes real actions in your workspace, so the same conversation can build the registration page, import the guest list, send the campaign and produce the post-event report. Your brand voice, fiscal calendar and defaults carry across every event.