Latido — wedding vendors & planning (Hungary)

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Search Hungarian wedding vendors and venues, check a date, estimate a budget, get the checklist.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Latido — wedding vendors & planning (Hungary)": {
      "url": "https://latido.wedding/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (8)

• search_vendors read-only

  Search Latido's public directory of Hungarian wedding vendors and venues (photographers, venues, DJs, florists, caterers, planners…). Use it whenever someone is looking for a supplier for a wedding in Hungary. Filter by category or top-level group, a place name (city, county or "Balaton"), maximum price in HUF, minimum seated capacity, a wedding style, or a date the vendor must be free on. Returns 10 results per page in the directory's own ranking; vendors who have not published a price/capacity/availability are kept (unknown is not a "no"). Each result has a public storefront URL — link to it. Does NOT search vendors who have not published a profile.

  Parameters:

  • area — string — Place name in Hungary — city, county or region ("Budapest", "Somogy", "Siófok"). Matches vendors based there OR travelling vendors who serve it.
  • page — integer — 1-based page, 10 results per page.
  • group — string — Top-level category: venues, photo_video, music_entertainment, … Use this for "any venue" / "a photographer".
  • query — string — Free-text match on the vendor name or tagline, e.g. "Makay" or "vintage". Leave empty to browse.
  • style — string — Wedding style the vendor works in (boho, rustic, classic, modern, glamour, folk_hu…). One style per search.
  • locale — string — Language for labels and copy. Use "hu" when the user writes Hungarian.
  • category — string — A specific subcategory, e.g. farm_barn, photographers, dj, vofely, cake. Narrower than `group`.
  • available_on — string — Wedding date (YYYY-MM-DD). Drops vendors KNOWN to be booked that day; vendors who do not publish availability are kept.
  • min_capacity — integer — Minimum seated guests (venues). Venues with no stated capacity are still returned.
  • max_price_huf — integer — Budget ceiling in HUF. Vendors with no published price are still returned.

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

• get_vendor read-only

  Full public storefront of one vendor or venue from Latido by id (from search_vendors): categories, where they work, price band, capacity, packages with prices, FAQ, links, published reviews and their own description. Use it after a search to answer detailed questions or to compare shortlisted vendors. Read-only; never returns contact details beyond the public links — the storefront URL is where a couple gets in touch.

  Parameters:

  • vendor_id (required) — string — The vendor id returned by search_vendors.
  • locale — string — Language for labels and copy. Use "hu" when the user writes Hungarian.

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

• list_categories_and_regions read-only

  The vocabulary search_vendors understands: the 11 top-level groups with their subcategory keys and labels, the wedding-style keys, and the Hungarian counties with their region ids. Call it once when you need to map what a user said ("vőfély", "pajta", "Balaton") onto a `group`/`category`/`style` value — do not guess keys.

  Parameters:

  • locale — string — Language for labels and copy. Use "hu" when the user writes Hungarian.

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

• check_availability read-only

  Whether one vendor (by id from search_vendors) is free, tentatively held, or booked on a given date — ONLY for vendors who chose to publish their availability. Most have not; then the answer is "unknown", which means "ask them", never "busy". Read-only.

  Parameters:

  • vendor_id (required) — string
  • date (required) — string — YYYY-MM-DD
  • locale — string — Language for labels and copy. Use "hu" when the user writes Hungarian.

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

• estimate_budget read-only

  A dated, sourced cost estimate for a wedding in Hungary (benchmark set hu-2026.1, as of 2026-08) from guest count, price tier, region and ceremony type — the same engine as latido.wedding/kalkulator. Returns a low/anchor/high total in HUF, the per-line breakdown, the marginal cost of one more guest, and the expected cash-gift income (Hungarian custom: gifts are cash). Use for "mennyibe kerül egy esküvő" questions. Estimates, not quotes; prices are in HUF.

  Parameters:

  • guests (required) — integer — Number of guests (adults + children).
  • date — string — Wedding date, if known — a weekday civil ceremony at the registry office is free.
  • tier — string — low = budget, mid = typical, high = premium.
  • locale — string — Language for labels and copy. Use "hu" when the user writes Hungarian.
  • region — string — budapest | videk (countryside) | unknown.
  • ceremony — string — civil | church (civil AND church) | abroad | undecided.
  • contingency_pct — integer

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

• wedding_checklist read-only

  Latido's planning checklist (Hungarian legal steps included: szándékbejelentés, documents, witnesses, name change), scheduled to a wedding date: every item with its phase, category and due date, compressed proportionally when the runway is shorter than 12 months. Filter by phase (start/book/shape/finish/week/after) and depth (essentials ≈27 · core ≈93 · everything ≈115). Use for "what should we be doing now" questions.

  Parameters:

  • depth — string
  • phase — string — Only this phase.
  • locale — string — Language for labels and copy. Use "hu" when the user writes Hungarian.
  • ceremony — string — civil | church | abroad | undecided — gates the Hungarian paperwork items.
  • wedding_date — string — YYYY-MM-DD. Without it, items come in order but undated.
  • planning_started — string — When planning began (YYYY-MM-DD); defaults to today. Sets how much the 12-month template is compressed.

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

• search read-only

  Free-text search over Latido's public Hungarian wedding vendor directory. Returns result ids for fetch. For filtered search (category, place, budget, capacity, date) prefer search_vendors.

  Parameters:

  • query (required) — string — Free-text query — vendor name, category or place.

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

• fetch read-only

  Full public storefront document for one result id from search. For a structured answer prefer get_vendor.

  Parameters:

  • id (required) — string — A result id from search.

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

Publisher website

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