Connect Nupty to your AI assistant
The Nupty connector lets an AI assistant work on your plan in Nupty while you chat: add the guests you dictate, compare vendor ideas, build the timeline of the day, keep the budget up to date. It uses the Model Context Protocol (MCP), the open standard behind the connectors of Claude, ChatGPT and Le Chat.
Connector URL
Add this URL as a custom connector. Your assistant then asks you to sign in to Nupty:
https://my.nupty.app/mcp
Without signing in, https://my.nupty.app/mcp/public offers one thing only: saving a plan (nupty.handoff v1) as a draft and giving you a link to it. You open the link, review the plan and sign up; drafts are kept encrypted for 7 days.
How to connect
Claude
- On claude.ai or the desktop app: Settings → Connectors → Add custom connector.
- Name: Nupty. URL: https://my.nupty.app/mcp. Add, then Connect.
- Sign in to Nupty in the window that opens and allow access. Turn the connector on in a chat when you want Claude to use it.
ChatGPT
- Settings → Apps & Connectors → Advanced settings: turn on developer mode (needed for custom connectors).
- Create a connector: name Nupty, MCP server URL https://my.nupty.app/mcp, authentication OAuth.
- Sign in to Nupty when asked and allow access.
Le Chat (Mistral)
- Intelligence → Connectors → Add connector → Custom MCP connector.
- Name: Nupty. Server URL: https://my.nupty.app/mcp. Choose OAuth.
- Sign in to Nupty and allow access.
Claude Code and other MCP clients
- claude mcp add --transport http nupty https://my.nupty.app/mcp — then /mcp in Claude Code to sign in.
- Any client that supports remote MCP servers with OAuth (dynamic client registration and PKCE) connects the same way.
The assistants rename their menus from time to time; look for “connectors” or “apps”.
What you allow
- You sign in with your Nupty account (e-mail or Google) and see what the assistant asks for: “Read and change your wedding plan in Nupty”.
- That covers your own wedding only — never payments, your account, API keys, sending invitations or publishing your website.
- Premium features stay Premium. Without Premium the assistant is told what needs it, with a link to the Premium page; it cannot buy anything.
- To stop it, disconnect it in Nupty (Settings → Connected assistants) or in your assistant’s settings.
Staying connected, and disconnecting
- Once connected, the assistant stays connected: you don’t sign in again for every chat. The connection lapses after 90 days without use, and after a year in any case; the assistant then asks you to sign in to Nupty again.
- Disconnect in Nupty: Settings → Connected assistants → Disconnect. The assistant loses access at once, in every chat. To use it again, connect it again and allow access anew.
- Disconnect in Claude: Settings → Connectors → Nupty → Disconnect, or remove the connector. In ChatGPT and Le Chat, remove or disconnect the connector where you added it. That makes the assistant forget the connection; to be sure nothing can use it any more, disconnect it in Nupty too.
What the assistant can do
The tools as the assistant sees them (generated from the same rules the planner uses, so this list is always complete). Their descriptions are in English.
| Tool | What it does | Kind |
|---|---|---|
create_wedding_draftCreate a wedding plan draft in Nupty | Saves a wedding plan prepared with the couple (nupty.handoff v1, see get_handoff_schema) as a draft and returns a link. The couple opens the link, reviews the plan, unticks what they do not want and signs up; nothing is added to any account before that. Drafts are deleted after 7 days. Leave out anything the couple has not decided. Names only for guests: no e-mail addresses, phone numbers, dietary or health details, links or payment data. | no sign-in |
get_handoff_schemaGet the plan format | Returns the JSON Schema of nupty.handoff v1, the wedding plan format create_wedding_draft accepts, with an example. | no sign-in |
get_plan_summaryGet the wedding plan summary | Reads an overview of the couple's wedding plan in Nupty: names, date, place, guest estimate, ceremony, style, currency, budget (target, planned, committed, paid), guest replies, vendors, Big Day moments and to-dos. | reads |
list_guestsList guests | Lists the invitations on the guest list with their people, side, group and RSVP reply (names only: no e-mail addresses, phone numbers or dietary notes). Filters by reply, side, group or part of a name; pages with offset/limit. | reads |
list_vendorsList vendors and vendor ideas | Lists the vendor types in the plan (venue, photographer, catering…) with status, budget, cost of the chosen idea, amount paid, and the vendor ideas (options) being compared under each. Amounts are whole units of the plan currency. | reads |
get_timelineGet the Big Day timeline | Reads the moments of the wedding day (time, name, length, linked vendor), in time order: the plan, or an alternative day version. Also lists the day versions; without Premium, alternative versions are read-only. | reads |
get_budgetGet the budget | Reads the budget: the total target, per vendor the planned budget, the cost of the chosen idea and what is paid, the all-in projection (min–max, counting undecided vendors from their ideas or budget) and every open payment by due date. Whole units of the plan currency. | reads |
list_todosList to-dos | Lists the to-dos (general ones and those under a vendor), open ones only unless includeDone is true. | reads |
list_change_setsList recent changes | Lists recent changes made to the plan from outside the planner (by assistants, API keys or a hand-off): when, by whom, what (in counts), and whether each can still be undone. | previews and undo |
update_wedding_detailsUpdate wedding details | Changes the wedding's basic details: the couple's first names, the date (exact or only the month), the guest estimate, ceremony type, style, currency, total budget target, place and 12h / 24h time display. Only the given fields change. | changes |
add_guestsAdd guests | Adds invitations to the guest list. Each entry is one invitation: a name ("Kati Nagy" or "Tamás & Éva Kovács"), an optional plus-one, number of children, side (p1, p2, both) and group. Names only: no e-mail addresses, phone numbers or dietary details. Names already on the list are skipped. Up to 300 per call. | changes |
update_invitationUpdate an invitation | Changes one invitation: its side, group, priority, whether it is for the whole day or the evening only, and its people's names. | changes |
set_rsvpRecord RSVP answers | Records RSVP answers the couple received by hand: yes (and who is coming), no, or waiting. "waiting" on an invitation not sent yet marks it as invited without e-mail (a paper or WhatsApp invitation; no free send is used). Answers recorded here show as "Manually entered". Up to 100 invitations per call. | changes |
remove_guestsRemove guests | Removes invitations from the guest list (and frees their seats). Needs confirmation: returns a preview and a confirm token; confirm_change applies it. | changes, after a preview |
add_vendor_ideasAdd vendor ideas | Adds vendor ideas to compare: either under a Nupty vendor type ("item": one of venue, stay, ceremonyloc, rentals, catering, cake, bar, sweets, latenight, officiant, rings, cermusic, music, booth, fireworks, kids, entertainment, photo, video, drone, creator, florist, decor, stationery, lighting, dress, suit, hair, alter, bridesmaids, transport, planner, gifts, honeymoon, favours) or under the couple's own type ("custom": its name, with a category). Each idea has a name and optionally a price (whole units of the plan currency) and a note. Ideas with the same name under the same type are skipped. Nothing is marked as booked. | changes |
update_vendorUpdate a vendor | Sets a vendor type's status (idea, comparing, booked, done) and/or its planned budget. | changes |
update_vendor_ideaUpdate a vendor idea | Changes one vendor idea: its name, fixed price or notes, or marks it as the chosen one for its vendor type. | changes |
remove_vendor_ideasRemove vendor ideas | Removes vendor ideas. Needs confirmation: returns a preview and a confirm token; confirm_change applies it. | changes, after a preview |
add_vendor_notesAdd vendor agreements and notes | Adds dated entries to vendor types' "Agreements & notes" log (e.g. "deposit due on signing", "menu tasting 12 March"). An entry with the same text under the same vendor is skipped. | changes |
add_timeline_itemsAdd Big Day moments | Adds moments to the wedding day (time HH:MM and a name, e.g. "15:00 Ceremony"): to the plan, or to an alternative day version (alternative versions need Premium). A moment with the same time and a similar name is skipped. | changes |
update_timeline_itemUpdate a Big Day moment | Changes the time, name or length of one moment of the wedding day (the plan, or an alternative version with Premium). | changes |
remove_timeline_itemsRemove Big Day moments | Removes moments from the wedding day (the plan, or an alternative version with Premium). Needs confirmation: returns a preview and a confirm token; confirm_change applies it. | changes, after a preview |
create_alternative_dayCreate an alternative day (Premium) | Copies the wedding day into a new alternative version the couple can change and compare with the plan (up to 4 versions). A Premium feature: without Premium the result says so and links to the upgrade page. | changes |
set_budget_linesSet budget lines | Sets the planned budget of vendor types (whole units of the plan currency; 0 = none). A suggested vendor type that gets a budget is added to the plan. Replacing more than one existing budget needs confirmation. | changes |
add_paymentsAdd payments | Adds payments (deposits, instalments) to vendor types: a label, an amount in whole units of the plan currency, an optional due date and whether it is already paid. Records them only; Nupty never moves money. | changes |
add_todosAdd to-dos | Adds general to-dos (a title and an optional due date YYYY-MM-DD). A to-do with the same title is skipped. | changes |
complete_todosTick off to-dos | Marks to-dos as done (or, with done: false, as open again). | changes |
remove_todosRemove to-dos | Removes to-dos. Needs confirmation: returns a preview and a confirm token; confirm_change applies it. | changes, after a preview |
confirm_changeConfirm a previewed change | Applies a change that was previewed with a confirm token (removals, or replacing several existing values). A token works once, for 10 minutes, and only if the plan still looks like the preview. | previews and undo |
undo_change_setUndo a change set | Reverts everything one earlier call changed (its change set), within 30 days. Refused if the couple or anyone else changed the same things afterwards. | previews and undo |
Previews, undo and the activity log
- Removing things, or replacing several existing values at once, never happens directly: the assistant gets a preview first and has to confirm it. A confirmation works once, for 10 minutes.
- Everything one request changes is one change set. You see it in Settings → Activity (“Claude (AI assistant) · added 37 guests”) and in a short note at the top of the planner, each with Undo, for 30 days.
- Undo is refused when you changed the same things afterwards, so it never overwrites your own edits.
Privacy
- The assistant sees your plan: names, dates, vendors, budget, the day’s timeline. Guests’ e-mail addresses, phone numbers and dietary needs are never shared with it.
- Nupty receives only what the assistant sends through these tools — never your chat.
- Your assistant’s provider (Anthropic, OpenAI, Mistral…) keeps your chats under its own terms.
Limits
- 240 changes and 600 reads a minute per assistant.
- Up to 64 KB per request (about 300 guests at a time).
Help
Questions or problems: [email protected]
What Nupty can do
The planner the couple gets, in seven areas. Each page lists every feature, marked Free or Premium, with a link to try it in the demo.
- Big Day timeline: The day moment by moment, the Stage your guests see and the Backstage your crew needs.
- Vendors & venue: Every quote in one place, compared side by side, from the first idea to booked.
- Guests & RSVP: The guest list, invitations and replies, per person.
- Seating & floor plan: Tables, seats and a floor plan to scale, in step with the replies.
- Budget & payments: A budget that follows your choices, and every payment until it is paid.
- Design Studio: Your wedding website and every printable, in one style, filled in from your plan.
- Account, sign-in & AI assistants: Signing in, Home and your to-dos, languages, and AI assistants that help with your plan.