Already planning with ChatGPT? Let it handle your guest texts too.
Connect your assistant to txt.wedding once, then just tell it what you need. It can build your guest list, sort everyone into groups, and draft the texts. You approve every message before a single guest hears from you. $1 per guest, one time.
How it works
Paste the link in your assistant
You do not need to sign up here first. When your assistant asks you to approve the connection, you can create your free account right on that screen, and then just tell your assistant your names and wedding date. Nothing is sent to anyone.
Connect your assistant
In ChatGPT or Claude, add txt.wedding as a connector and paste this link when it asks for one. It will have you sign in, so it only ever sees your wedding.
https://txt.wedding/mcp- ChatGPT: Settings, then Connectors, then add a custom connector with this link.
- Claude: Settings, then Integrations or Connectors, then add this link.
Paste a prompt and go
Just talk to your assistant like you already do. Try this first one to check everything is connected:
Connect to txt.wedding and tell me which wedding you can see, how many guests are on it, and whether it is ready to send.
Try one of these
Once your assistant is connected, these work word for word. Copy one, paste it in, and it does the rest.
Start here
Confirm the connection and see what your assistant can reach.
Connect to txt.wedding and tell me which wedding you can see, how many guests are on it, and whether it is ready to send.
Build the guest list
Hand over a messy list and let your assistant clean it up.
Add these guests to my wedding on txt.wedding and put them in a group called Family. Tell me any phone numbers you could not use and why.
Here is my guest list. Add everyone to txt.wedding, then show me duplicates and anyone missing a phone number so I can chase them.
Organize groups
Groups let you text the right subset instead of everyone.
Split my txt.wedding guest list into Family, Wedding party, and Out of town, and show me the count in each group.
Draft and check before sending
Nothing goes out until you say so.
Draft a day-of text telling guests the ceremony moved to 4:30pm at the same venue. Keep it under 160 characters, then run the txt.wedding send check and show me the result before sending anything.
Before we send anything, check my txt.wedding send readiness: how many guests my plan covers, whether my phone is verified, and who has opted out.
Send, with your approval
You confirm the exact words and the exact audience.
Send a test of this message to my own phone on txt.wedding first, then wait for me to confirm before sending it to guests.
Send the message I just approved to the Out of town group only. Do not send to anyone else.
After the day
Catch up on replies and the photos guests sent in.
Summarize the replies from my guests on txt.wedding and flag anything that needs a human answer from me.
Show me what we sent for my wedding on txt.wedding, how many guests got each message, and how many photos guests uploaded.
You're always in control
- Your assistant signs in as you. It only ever sees your own wedding.
- Nothing is ever sent without your approval. You see the exact words and the exact guests first.
- Every message passes the same safety checks as if you sent it yourself.
- Guests who reply STOP stay opted out. Your assistant cannot undo that.
- It never touches payments, refunds, or anyone else's wedding.
Bring your own assistant
Start your wedding, then let ChatGPT or Claude handle the guest list and the day-of texts.
For planners and developers
txt.wedding is the agent-first platform for wedding guest communication. The connect link above is a standard MCP server endpoint, so any MCP client (ChatGPT, Claude, Cursor, or your own agent) can use it with OAuth sign-in. Machine-readable product facts live at txt.wedding/llms.txt.
Tools your agent gets
- list_weddings — your weddings, dates, and payment state
- get_wedding — one wedding with guest, opt-out, and message counts
- list_guests — guests with phone, groups, and opt-out status
- add_guest — adds one guest, optionally into a group
- list_groups — guest groups and their sizes
- list_messages — what you have already sent
- list_replies — inbound replies from guests
- list_uploads — photos and videos guests uploaded
- check_send — dry run: plan coverage and who would be skipped
- send_message — sends for real, only with your approval