Planning your wedding with AI? We have the tools for your agents.
txt.wedding is the guest list and guest messaging layer your assistant can actually operate. Connect ChatGPT, Claude, Cursor, or your planner's own agent to your account, then use the prompts below. Your agent drafts and checks. You approve every text that reaches a guest. $1 per guest.
Connect your assistant
Add txt.wedding as a custom MCP connector in your assistant, then sign in with your txt.wedding account when it asks. Read-only tools work immediately; sending needs your approval each time.
https://txt.wedding/mcpNo txt.wedding account yet? , add your wedding, then connect.
Prompts to copy
These work word for word once the connector is added. Paste one in and your agent 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.
What your agent can and cannot do
Tools it 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
Guardrails
- Your agent signs in as you. It only ever sees your own weddings.
- Every send passes the same content, volume, and opt-out checks as the app.
- A partial send is refused unless you approve the covered subset yourself.
- No access to payments, refunds, or anyone else's data.
- Guests who reply STOP stay opted out. An agent cannot undo that.
Bring your own assistant
Start your wedding, then let your agent handle the guest list and the day-of texts.