Wedyesday — wedding planning

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

Plan a wedding in chat: search vendors, get regional costs, build a checklist and budget.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Wedyesday — wedding planning": {
      "url": "https://mcp.wedyesday.com",
      "transport": "streamable-http"
    }
  }
}

Measured tools (12)

• list_wedding_markets read-only

  List the countries, regions and vendor categories Wedyesday supports, with the exact values to pass to the other Wedyesday tools. Call this first when you do not already know a valid country code, region slug or vendor category.

  Parameters:

  • country — string — Optional ISO country code (AU, US, GB, NZ, IN). Supply it to list that market's regions.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• search_wedding_vendors read-only

  Search Wedyesday's directory of wedding vendors — venues, photographers, caterers, florists, celebrants and more. Returns real published listings with ratings, price bands and a link to each profile. Use list_wedding_markets first if you are unsure which category or country code to pass.

  Parameters:

  • city — string — City name, e.g. "Melbourne" or "London".
  • limit — integer — Maximum results, 1-25. Defaults to 8.
  • query — string — Free-text search, e.g. "barn" or "documentary style".
  • region — string — State or region, e.g. "VIC" or "California".
  • country — string — ISO country code: AU, US, GB, NZ or IN. Pass the couple's country; defaults to AU, the first market with a live vendor directory.
  • category — string — Vendor category, e.g. "venue" or "photography". One of: venue, photography, videography, catering, flowers, planning, dj, band, ceremony_music, beauty_health, dress_attire, cake, transportation, event_rentals, photo_booth, lighting_decor, invitations, officiant, jewelry, travel.
  • minRating — number — Minimum average review rating, 1-5.
  • priceBands — array — Filter by price band. Any of: budget, standard, premium, luxury, quote_required.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_wedding_cost_guide read-only

  Get typical wedding costs for a region — a low/typical/high total plus a category-by-category breakdown (venue, catering, photography and so on). Use this to answer 'how much does a wedding cost' questions with real regional figures rather than estimates.

  Parameters:

  • region — string — Region slug from list_wedding_markets, e.g. "melbourne" or "london". Omit for the national figure.
  • country — string — ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — figures are per market; defaults to AU when omitted.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_wedyesday_pricing read-only

  Get what Wedyesday itself costs in a country — wedding-website add-ons for couples and vendor plans for businesses — in the currency that market is charged in, with a link to that country's published price list. Use this to answer 'how much does Wedyesday cost' instead of converting currencies. Planning tools, publishing a wedding website and enquiring with vendors are free.

  Parameters:

  • country — string — ISO country code: AU, US, GB, NZ or IN. Pass the buyer's country — prices differ per market; defaults to AU when omitted.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• build_wedding_plan read-only

  Build a personalised wedding plan: a month-by-month checklist with real due dates, a budget split for the couple's region, and how their budget compares to typical local spend. This is the same planning engine as the Wedyesday website, so nothing here is invented. Nothing is saved and no account is needed — follow up with create_wedyesday_workspace_link when the couple wants to keep it.

  Parameters:

  • guestCount (required) — integer — Expected number of guests, 2-2000.
  • budget — integer — Total budget in whole currency units (e.g. 45000). Omit if the couple does not have one yet — a regional typical figure is used instead.
  • region — string — Region slug from list_wedding_markets, e.g. "melbourne" or "london". Drives the budget split and legal steps.
  • season — string — Required when dateMode is "season".
  • country — string — ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — the legal steps and budget split depend on it; defaults to AU when omitted.
  • dateMode — string — "fixed" when the date is set, "season" when only a season and year are known, "undecided" otherwise.
  • location — string — Where the wedding is, e.g. "Melbourne, VIC" or "London".
  • eventDate — string — Wedding date as YYYY-MM-DD. Required when dateMode is "fixed".
  • partnerOne — string — First partner's first name.
  • partnerTwo — string — Second partner's first name.
  • priorities — array — Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling.
  • seasonYear — integer — Year for the chosen season.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• create_wedyesday_workspace_link

  Turn a wedding plan into a private link the couple can open to save it as a free Wedyesday workspace — checklist, budget, guest list, RSVPs and a wedding website. Pass the same answers used for build_wedding_plan. This creates no account and stores no personal details; the couple signs up themselves when they open the link. Give them the link and tell them it expires in 14 days.

  Parameters:

  • guestCount (required) — integer — Expected number of guests, 2-2000.
  • budget — integer — Total budget in whole currency units (e.g. 45000). Omit if the couple does not have one yet — a regional typical figure is used instead.
  • region — string — Region slug from list_wedding_markets, e.g. "melbourne" or "london". Drives the budget split and legal steps.
  • season — string — Required when dateMode is "season".
  • country — string — ISO country code: AU, US, GB, NZ or IN. Pass the couple's country — the legal steps and budget split depend on it; defaults to AU when omitted.
  • dateMode — string — "fixed" when the date is set, "season" when only a season and year are known, "undecided" otherwise.
  • location — string — Where the wedding is, e.g. "Melbourne, VIC" or "London".
  • eventDate — string — Wedding date as YYYY-MM-DD. Required when dateMode is "fixed".
  • partnerOne — string — First partner's first name.
  • partnerTwo — string — Second partner's first name.
  • priorities — array — Up to three things that matter most. Values: venue, photography, food, music, flowers, videography, attire, styling.
  • seasonYear — integer — Year for the chosen season.

  Hints: read-only no · destructive no · idempotent no · open-world no

• get_my_wedding_dashboard read-only

  Get an overview of the signed-in couple's Wedyesday wedding: date, countdown, checklist progress, budget position and what is due next, plus a direct link to their dashboard. Start here for any question about 'my wedding'. Requires a connected Wedyesday account.

  Parameters:

  • weddingId — string — Only needed when the account has more than one wedding.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_my_wedding_tasks read-only

  List tasks from the couple's Wedyesday checklist, newest deadlines first. Filter to what is overdue, due soon, or already done. Requires a connected Wedyesday account.

  Parameters:

  • limit — integer — Maximum tasks to return, 1-40. Defaults to 15.
  • filter — string — "open" (default) for everything not done, "overdue", "done", or "all".
  • weddingId — string — Only needed when the account has more than one wedding.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• add_my_wedding_task

  Add a task to the couple's Wedyesday checklist. Confirm the wording and the due date with the couple before calling this — it writes to their real workspace. Requires a connected Wedyesday account.

  Parameters:

  • title (required) — string — What needs doing.
  • dueDate — string — Due date as YYYY-MM-DD.
  • category — string — Optional grouping, e.g. "Venue" or "Attire".
  • weddingId — string — Only needed when the account has more than one wedding.
  • description — string — Optional detail.

  Hints: read-only no · destructive no · idempotent no · open-world no

• complete_my_wedding_task

  Mark a task on the couple's Wedyesday checklist as done. Get the task id from list_my_wedding_tasks first, and confirm with the couple which task they mean. Requires a connected Wedyesday account.

  Parameters:

  • taskId (required) — string — Task id from list_my_wedding_tasks.
  • note — string — Optional note recorded against the completion.
  • weddingId — string — Only needed when the account has more than one wedding.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• get_my_wedding_budget read-only

  Get the couple's Wedyesday budget: planned versus actual by category, what is left, and any payments due or overdue. Requires a connected Wedyesday account.

  Parameters:

  • weddingId — string — Only needed when the account has more than one wedding.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_my_guest_list read-only

  Get a summary of the couple's Wedyesday guest list: headcount, groups, how many have contact details on file, plus_ones and children. Guests' email addresses and phone numbers are never returned — those stay in the dashboard. Requires a connected Wedyesday account.

  Parameters:

  • weddingId — string — Only needed when the account has more than one wedding.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.