Changelog

Changes that affect integrations, newest first.

2026-10-23

• New MCP address. The MCP server's advertised address is now https://mcp.wedstay.com/api/ai/mcp, in the discovery card, llms.txt and these docs. The same server still answers at https://www.thewedstay.com/api/ai/mcp, so clients set up with it keep working.
• Tour requests on MCP. New write tool submit_tour_request saves a tour request (in person or live video) and returns call_url, the link to book the couple's call with the WedStay team; the request is sent once that call is booked. It is marked like the other write tools and needs the couple's explicit go-ahead. tools/list now returns 26 tools, every existing tool unchanged in name and place. See submit_tour_request.
• Tour mode in the form. show_inquiry_form takes optional request_type (booking or tour) and tour_format (in_person or virtual), and its view carries tours_available. The form gains a Book and Tour switch; Book works as before. See ChatGPT.

2026-10-20

• sms_consent is optional on MCP. submit_venue_inquiry and submit_vendor_inquiry accept a call without sms_consent. Ask the couple whether WedStay may text them and pass their answer; without it, WedStay replies by email only, and the inquiry records that the couple was not asked. The REST inquiry endpoints still require it. See MCP Server.
• Inquiry tools marked destructive. Both MCP submit tools now carry destructiveHint: true, because a sent inquiry cannot be unsent. Their other hints are unchanged.
• View tools and app-only helpers. Six tools show WedStay's own views in clients that display MCP Apps: show_venues, show_venue_comparison, show_pricing_breakdown, show_inquiry_form, open_venues and open_shortlist. Other clients get a short text line. Three helpers used only by those views, shortlist_get, shortlist_add and shortlist_remove, keep a shortlist for one conversation. The other 14 data tools are unchanged. See Venue views.
• Resources advertised. initialize and server/discover now advertise resources (with listChanged: false) for the two view documents, ui://wedstay/cards-v1.html and ui://wedstay/app-v1.html.

2026-10-08

• MCP server 2.0.0. The server at https://www.thewedstay.com/api/ai/mcp now reports version 2.0.0.
• sms_consent is required. submit_venue_inquiry, submit_vendor_inquiry and the REST inquiry endpoints require a boolean sms_consent. Ask the user whether WedStay may text them about the request. A missing or non boolean value returns 400 with code sms_consent_required. See Inquiries.
• Per stay pricing object. Venue results carry a structured pricing object for the stay, in the same currency the listing shows. See Venues.
• budget_max. search_venues accepts budget_max, compared against each venue's starting price in the listing's own currency.
• calculate_pricing slug mode and strict regions. Pass a venue slug to price that venue with the same engine as its page. Regions must be one of the listed ids or aliases; an unknown region returns an error. See Pricing.
• Benchmark keys. Cost benchmarks use *_base_per_stay keys. The *_nightly aliases are deprecated and will be removed on 2027-01-06.
• Rate limit headers. Every 429 carries Retry-After, and X-RateLimit-Reset is a Unix timestamp in seconds. See Rate Limits.