Plan your wedding in Ringske: manage guests, RSVPs, tasks, budgets, vendors, and schedules. Sign in with your Ringske account via OAuth.
Scored across 46 tools
The tools are mostly cleanly separated by resource and action across budget, guests, moments, seating, schedule, tasks, vendors, and ideas. A few boundaries require careful reading, especially guest RSVP updates versus seating changes, and vendor booking versus expense creation, but the descriptions generally resolve these.
Names consistently use kebab-case verb-noun phrasing such as add-guest, update-vendor, delete-task, and get-budget. Minor variants like get-wedding-overview, seat-guest, and mark-payment-paid still fit the overall predictable convention.
With 46 tools, the surface is very large for a wedding-planning server and exceeds the threshold where tool selection becomes cumbersome. While the domain is broad, many add/update/delete groups could likely be consolidated or scoped more tightly.
Coverage is strong across most core wedding-planning domains: guests, moments, tasks, vendors, seating, schedule, ideas, budget categories, expenses, thank-yous, and read-only overview/logbook views. Remaining gaps include payment instalment creation/editing, payer update/delete, and management of custom RSVP questions, though several appear intentionally delegated to the dashboard.
Adds a category to the budget (e.g. "Honeymoon"), optionally with the amount the couple plans to spend on it. Every couple starts with the usual categories; get-budget lists them. A category that already exists is not added twice.
Inputs: name (required), planned_amount.
Adds an expense to the budget with a fixed amount, e.g. the dress or the rings. A booked vendor already gets its expense automatically; link one with vendor_id instead of adding it twice.
Inputs: name (required), notes, amount, category, +2 more.
Adds an invitation to the guest list, e.g. "Andrea & Michael" (counted as 2 unless a size is given). Invited to the given moments, or to every moment that guests can see when none are given. Use update-guest afterwards to write down an answer.
Inputs: name (required), size, email, notes, +5 more.
Adds a note to the couple's shared ideas: a thought, a measurement, a song, a question for a vendor. Both partners see it in the dashboard.
Inputs: body (required), title, pinned.
Adds a moment of the wedding day that guests can be invited to (e.g. "Walking dinner"). Without a date it takes the wedding date, without a location the venue. A dinner gets fixed seats (a seating plan) unless seated is false. Invite guests to it with update-guest.
Inputs: name (required), date, type, notes, +9 more.
Adds someone who pays part of the wedding, e.g. "Ouders Elian". Every couple starts with both partners and "together"; get-budget shows what each payer paid and still has to pay. Which payer pays an instalment is set in the dashboard.
Inputs: name (required).
Adds an item to the run of show (draaiboek) of the wedding day, e.g. "14:00 Ceremony". Items marked for_guests also appear in the programme on the wedding website.
Inputs: title (required), notes, owner, location, +6 more.
Adds one or more tables to the seating plan of a moment with fixed seats (usually the dinner), e.g. "10 round tables of 8". Without a name they are numbered after the tables that exist ("Tafel 4"). Leave out moment_id when only one moment has fixed seats.
Inputs: name, count, seats, shape, +1 more.
Adds a task to the planner. The deadline is either a date (due_date) or a number of days relative to the wedding date (offset_days, e.g. -42 for six weeks before), which moves along when the wedding date changes.
Inputs: title (required), notes, due_date, offset_days, +1 more.
Adds a vendor to compare: a venue, caterer, photographer, band, florist, … Starts on the shortlist unless a status is given; a booked vendor is put in the budget automatically.
Inputs: name (required), category (required), email, notes, +10 more.
Deletes a budget category and its planned amount. Its expenses stay in the budget, without a category. Confirm with the user first.
Inputs: id (required).
Deletes an expense from the budget, with its payments and attached receipts. Cannot be undone: confirm with the user first.
Inputs: id (required).
Removes an invitation from the guest list, with its answers and seats. Cannot be undone: confirm with the user first.
Inputs: id (required).
Deletes a note from the couple's ideas, for both partners. Cannot be undone: confirm with the user first.
Inputs: id (required).
Deletes a moment, with every invitation and answer for it and its seating plan. The guests stay on the list. Cannot be undone: confirm with the user first, and say how many invitations it has (list-moments).
Inputs: id (required).
Deletes an item from the run of show (and so from the programme on the website). Confirm with the user first.
Inputs: id (required).
Removes a table from the seating plan. Whoever sat there goes back to the guests still to seat; nobody is removed from the guest list. Confirm with the user first when people sit at it.
Inputs: table_id (required).
Deletes a task from the planner. To finish a task, use update-task with status done instead. Confirm with the user first.
Inputs: id (required).
Deletes a vendor with its ratings and documents (quotes, contracts). Its expenses stay in the budget. To drop a vendor from the comparison, prefer update-vendor with status rejected. Confirm with the user first.
Inputs: id (required).
The budget: total budget, committed, paid and left, planned versus committed per category (with their ids), what each payer paid and still has to pay, upcoming payments (with their ids, for mark-payment-paid) and every expense. A per-guest expense follows the RSVPs of its moment.
Inputs: no named parameters.
Everything about one invitation: size and children, whose guest, contact details and postal address, the answer per moment, dietary notes, the message they left, answers to the couple's RSVP questions and their personal RSVP link.
Inputs: id (required).
The logbook (the "Logboek" page): who did what, newest first. Which partner added or removed a guest, invited someone to a moment, sent an invitation or a card, ticked off a task or booked a vendor; which guest answered; what Ringske sent by itself. Use it for "did Moya already invite Aunt Rita?" or "what happened this week?".
Inputs: days, limit, topic.
Where the RSVPs stand: counts per moment, the dietary list for the caterer, the messages guests left, the couple's own RSVP questions (kind, options, whether required) with their answers, and answers that could not be matched to a guest.
Inputs: no named parameters.
The run of show for the wedding day (draaiboek): every item in order with time, duration, place, who is responsible, linked vendor and moment, and whether guests see it in the programme on the website. Plus the contact list for the day.
Inputs: no named parameters.
The seating plan of a moment with fixed seats (usually the dinner): every table with who sits there, and who still needs a seat. Tables are shown as [table 3], invitations as [id 12]; change the plan with add-seating-table, seat-guest and unseat-guest.
Inputs: moment_id.
The big picture of the wedding: date and days to go, the moments with their RSVP counts, guests, open and overdue tasks, budget and vendors. A good first call.
Inputs: no named parameters.
The couple's shared ideas and notes (the "Ideeën" page): loose thoughts, measurements, songs, questions for vendors. Pinned notes first.
Inputs: query.
Lists the moments of the wedding day (ceremony, reception, dinner, party, …) with time, place and RSVP counts in people: invited, yes, no and not answered, children counted among them. Use the ids to filter guests per moment.
Inputs: no named parameters.
Lists the couple's tasks with their deadline, status and planning phase, soonest deadline first. Filter on status (open, todo, doing, done, overdue), on phase or on words in the title.
Inputs: limit, phase, query, status.
After the wedding: per invitation what they gave and whether the thank-you card went out, with the postal address for the card. By default the invitations that said yes to a moment (they came) and still need thanking; use filter and everyone to see more. Note a gift or a sent card with update-thank-you.
Inputs: filter, search, everyone.
Lists the vendors the couple is comparing or booked (venue, catering, photography, music, …) with status, quote, rating, follow-up date and contact details. Filter on category or status.
Inputs: status, category.
Marks an open payment (an instalment of an expense, e.g. a deposit) as paid today, or on the given date; the budget totals follow. On a payment that is already paid, it overwrites the paid date. Payment ids come from get-budget.
Inputs: payment_id (required), paid_on.
Searches the guest list. Answers questions like "who has RSVP'd yes for the dinner?", "who hasn't answered yet?", "who is vegetarian?" or "which cards still have to go out?". Each result is one invitation with its size and its answer per moment.
Inputs: limit, query, offset, status, +5 more.
Seats an invitation at a table of the seating plan: everyone of the party without a seat yet, or the given number of seats to split a party over tables. A party that already sits at exactly one other table is moved; to move from one of several tables, pass from_table_id. Only invitations that said yes or have not answered get a seat. A table may go over capacity.
Inputs: guest_id (required), table_id (required), seats, from_table_id.
Takes an invitation off a table of the seating plan: everyone of the party seated there goes back to the guests still to seat. Also how to clear a seat of someone who is no longer coming. The guest stays on the guest list.
Inputs: guest_id (required), table_id (required).
Sets the total budget of the wedding, the amount the couple wants to stay under. An empty value or 0 removes it. The planned amount per category is set with update-budget-category.
Inputs: total (required).
Sets the amount the couple plans to spend on a budget category, or renames it. Only the fields you pass change; an empty planned_amount or 0 clears it. Category ids come from get-budget.
Inputs: id (required), name, planned_amount.
Changes an expense: name, amount, category, linked vendor or notes. Only the fields you pass change. A per-guest expense takes per_guest_amount instead of amount. Payment instalments are managed in the dashboard; mark one as paid with mark-payment-paid.
Inputs: id (required), name, notes, amount, +4 more.
Changes an invitation: its details, and the answers per moment — for an RSVP the couple got by phone or in person. Only the fields you pass change; pass null or an empty string to clear a text field. Set an answer to not_invited to take the invitation to that moment back.
Inputs: id (required), city, name, size, +12 more.
Changes a note in the couple's ideas: title, text or whether it is pinned. Only the fields you pass change; the old text is overwritten.
Inputs: id (required), body, title, pinned.
Changes a moment: name, kind, date and times, place, capacity, whether guests see it, whether it has fixed seats (a seating plan), notes and the text for guests who are not invited. Only the fields you pass change; pass null or an empty string to clear a text field.
Inputs: id (required), date, name, type, +10 more.
Changes an item of the run of show: time, duration, title, place, who is responsible, linked vendor or moment, and whether guests see it. Only the fields you pass change.
Inputs: id (required), notes, owner, title, +7 more.
Renames a table of the seating plan or changes its seats, shape or notes. Only the fields you pass change. Fewer seats than people seated is allowed: the table is then over capacity.
Inputs: table_id (required), name, notes, seats, +1 more.
Changes a task: its status (todo, doing, done), title, notes or deadline. Only the fields you pass change. Setting due_date removes an offset deadline and the other way round; pass both as null to remove the deadline.
Inputs: id (required), notes, title, status, +2 more.
Notes what an invitation gave, and whether their thank-you card was sent (today) or not after all. Only the fields you pass change; an empty gift clears it. The logbook records that someone was thanked, never what they gave.
Inputs: id (required), gift, thanked.
Changes a vendor: move it along (contacted, quoted, booked, rejected), record a quote, a follow-up date or contact details. Only the fields you pass change. Booking puts the vendor in the budget; a later quote updates that expense.
Inputs: id (required), name, email, notes, +11 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
