OpenApps

Aisle MCP server — tools & history

Aisle MCP server: observed open status, tool schemas, linked apps and version history.

Aisle

Endpoint: https://aisle.wedding/api/claude/mcp

Observed status: open. Checked: 2026-10-12T05:06:41+00:00.

Linked apps

  • Aisle

    Find wedding venues and suppliers, plan budgets and timelines, and manage wedding details, guests and events with your AI assistant.

Observed tools

  • add_my_accommodation — Adds an unpriced room under a named property in the selected wedding. Property and room names are required. The new room has no payment requirement. Requires sign-in and an Aisle membership.
  • add_my_event — Creates an event in the selected wedding, with its name, type, date, time and optional venue, dress code and description. Requires sign-in and an Aisle membership.
  • add_my_guest — Adds a guest to the selected wedding after explicit confirmation that the person is 13 or older, before collection of their name or contact details. First and last names are required; phone and email are optional. Results return the saved guest details. Age cannot be inferred from names or relationships. Guest notes and dietary details are unsupported. Requires sign-in and an Aisle membership.
  • generate_wedding_hashtags — Generates deduplicated wedding hashtag suggestions from partner names, surnames, year and place, ordered by a deterministic score. Suggestions are not registrations or availability checks.
  • get_alcohol_estimate — Estimates wedding bar quantities from guest count, event duration and drink mix, with bottles and cases rounded up. Quantities follow planning rules of thumb and are not a guarantee of consumption. This tool does not purchase alcohol.
  • get_budget_estimate — Estimates a whole destination wedding budget in USD by guest count, place and style tier, from Aisle’s modelled wedding cost index. Accepts a destination or a country; a destination without a row of its own is priced at its country and the result says so. Results include a line-by-line breakdown, a typical total and the range most weddings land in. Places the index does not cover return coverage information. Figures are modelled estimates, not supplier quotes or prices from booked weddings.
  • get_cash_gift_suggestion — Returns an illustrative low, typical and high cash wedding gift range in USD based on relationship, attending party, travel and wedding-party role. Results describe US etiquette conventions, not obligations. This tool does not transfer money.
  • get_day_of_timeline — Builds a draft wedding-day schedule around the ceremony time, first-look preference and reception duration. Times use standard planning offsets rather than confirmed vendor, venue or sunset schedules.
  • get_dress_code_guide — Returns a wedding dress code definition, clothing examples and invitation wording, or lists the available dress codes when none is specified. Results include the corresponding Aisle guide link.
  • get_guest_travel_estimate — Estimates round-trip flights and lodging in USD for guest groups departing from supported US metros. Stay length and guests per room can be set, and default to the destination’s typical stay in a private room per guest. Partial totals include only priced groups; unpriced guests and unsupported origins are reported separately. The urlRestoresEstimate field states whether the returned web link restores the supplied groups. Estimates are not live fares or bookings.
  • get_invitation_wording — Composes wedding invitation text for a hosting situation and formality, using supplied names, event details and optional reception wording. With no scenario, it lists available options. Wording follows etiquette conventions rather than legal requirements.
  • get_my_guest — Returns one identified guest recorded as 13 or older in the selected wedding, with saved names, contact preferences (a "defaulted" list names any nobody chose), language, RSVP status and timestamps. Missing, other-wedding, under-13 and unconfirmed-age records return the same not-found result. Guest notes and dietary details are excluded. Requires sign-in.
  • get_my_wedding — Returns the signed-in account's selected wedding details, including partner names, date, location and venue. Access is limited to weddings the account can manage.
  • get_my_wedding_stats — Returns aggregate wedding statistics, including guest totals across all age bands, RSVP counts, event counts and registry progress. Responded counts attending and declined guests; outstanding counts pending and maybe guests; the response rate is responded as a percentage of all guests. Guest identities and individual event answers are excluded. Requires sign-in.
  • get_packing_list — Returns a destination wedding packing list by climate and role, covering clothing, weather essentials, travel documents and practical supplies.
  • get_planning_timeline — Returns a destination wedding planning timeline organized by months before the wedding, from venue planning through day-of logistics.
  • get_vendor_details — Returns a published wedding vendor by its slug, including services, descriptions, FAQs, ratings, photos and website links. The result states whether the description, services and FAQs were generated by Aisle from public information or supplied by the vendor, gives a price band only when the vendor supplied one, whether the vendor chose its category, and where the rating comes from.
  • get_venue_details — Returns a published wedding venue by its slug, including photos, highlights, travel information, planning estimates and available sourced facts with provenance. An estimators block names the destination the budget and guest travel estimators accept for the venue, the country when its area has no budget row, and covered destinations in the same country when travel has no figures for its area. Estimates are not supplier quotes or live availability.
  • get_wedding_checklist — Returns destination wedding planning milestones across eight phases, from eighteen months before the wedding through the day itself. An optional month limit narrows the milestones shown.
  • get_who_pays_split — Calculates percentages and amounts for dividing a wedding budget among the couple and their families under a selected model. Traditional assignments describe etiquette conventions, not obligations. This tool does not transfer money.
  • list_my_accommodations — Lists the selected wedding's places, including empty places with ids, active room counts, stored room-choice overrides and effective modes, plus room descriptions, capacity, status, stay details, stored price and deposit overrides in property order. Guest assignments and occupant identities are excluded. Requires sign-in.
  • list_my_events — Lists the selected wedding's events in date order with their dates, times, venues, dress codes and descriptions. Optional filters narrow results by event type or by a range of calendar days in the wedding's time zone; the total counts the events returned. Each event names the other events whose times overlap it. Requires sign-in.
  • list_my_guests — Lists guests in the selected wedding who are recorded as 13 or older, with saved names, contact preferences (a "defaulted" list names any nobody chose), language, RSVP status and timestamps. Optional filters narrow results by RSVP status, language or name, and results can be ordered by name or by most recent update, RSVP reply or addition; per-status counts cover every listed guest before filtering. Guests under 13 or with unconfirmed ages are excluded, as are guest notes and dietary details. Requires sign-in.
  • list_my_registry — Lists the selected wedding's registry and honeymoon fund items, descriptions, goal amounts and received totals. Donor identities are excluded. This tool does not collect contributions or initiate payments. Requires sign-in.
  • list_vendor_categories — Lists every wedding vendor category and its published listing count, optionally filtered by location. A category with no listings is included with a count of 0.
  • list_venue_countries — Lists countries with published wedding venues on Aisle and the number of venues in each country, broken down by venue type and by searchable price band, with a count of venues that have no price band.
  • remove_my_accommodation — Removes an identified room and its guest assignments from the selected wedding, subject to payment and checkout safeguards. Uncharged checkouts without a payment method require confirmed cancellation. Completed, refunded or processing payments and active checkouts with a card prevent removal. Payment history is retained. The place is retained unless remove_empty_place is set and the place has no other rooms or retained history; otherwise empty places require a separate explicit removal. Requires sign-in and an Aisle membership.
  • remove_my_event — Removes an identified event from the selected wedding and returns the removed event's id and name. Requires sign-in and an Aisle membership.
  • remove_my_guest — Removes an identified guest already recorded as 13 or older from the selected wedding and returns the removed guest's id and name. Guests under 13 or with unconfirmed ages are ineligible. Requires sign-in and an Aisle membership.
  • remove_my_place — Removes an identified empty place from the selected wedding and its property order, and returns the order that remains. The places list supplies its id. This removes any recommendation or booking link on that place. Any rooms, including archived history, prevent removal. No rooms or payments are deleted. Requires sign-in and an Aisle membership.
  • reorder_my_places — Sets the order of all properties on the selected wedding's guest site and accommodation screen. The complete list is required, as property ids from the places list or as names; name matching ignores case and surrounding spaces. Results and refusals give the order as ids with names. Partial or invalid lists are refused with the current order. Requires sign-in and an Aisle membership.
  • search_guides — Searches Aisle wedding planning guides by keywords and returns up to 10 relevant excerpts with links to the full articles and the date each guide was last revised, at most 3 from any one guide unless a different per-guide limit is supplied.
  • search_vendors — Searches published wedding vendors by category, location and price range. Results include business details and listing links, with totals and pagination; summary omits descriptions and images. Each result states whether its content was generated by Aisle from public information or is managed by the vendor, where its rating comes from, whether its category was chosen by the vendor or assigned by Aisle’s search, and the domain of its website. A price band is reported, and matched by the price filter, only when the vendor supplied it. Results can be filtered by minimum Google rating and review count, and ordered by name, rating or review count. When a location holds fewer than five matching vendors, the result lists nearby locations within 150km that hold more, with counts and distances. A location search also gives each vendor’s distance from the middle of that location’s listings, since the listed city is the place searched rather than the vendor’s own town. This search does not check live availability or make bookings.
  • search_venues — Searches published destination wedding venues by country, venue type, guest capacity and price range, optionally leaving out unverified imported listings. Results include descriptions, photos and listing links, with totals and pagination; summary omits descriptions and images. Unknown capacity and unverified imported price bands are null. This search does not check live availability or make bookings.
  • set_my_property_room_selection — Sets room choice for one Hosted property in the selected wedding. The property is identified by id or an exact, unambiguous name; matching ignores case and surrounding spaces. A non-null mode selects couple assignment or guest choice. Null restores the legacy wedding fallback. Other properties retain their settings. Results return the property id, stored override and effective mode. Requires sign-in and an Aisle membership.
  • set_my_site_address — Changes the selected wedding's guest-site address within aisle.wedding, retaining redirects from its previous address. Addresses use 2 to 63 lowercase letters, numbers or hyphens and must be available and unreserved. Requires sign-in and an Aisle membership.
  • update_my_accommodation — Updates supplied room details, pricing, payment requirements or deposit and balance schedules in the selected wedding. Omitted fields remain unchanged. Null clears the room type, description, stay dates, check-in and check-out times or check-in notes. Setting a price enables payment unless explicitly disabled; zero makes the room free. Results return the saved room details, identify saved changes with their previous values and describe whether payment is available. This tool does not initiate a charge. Requires sign-in and an Aisle membership.
  • update_my_event — Updates supplied name, type, schedule, venue, dress code or description fields for an identified event in the selected wedding. Omitted fields and existing invitations and responses remain unchanged. Null clears the end time, venue, address, dress code or description. Results identify saved changes with their previous values. Requires sign-in and an Aisle membership.
  • update_my_guest — Updates supplied name, contact, RSVP, communication preferences or language for a guest already recorded as 13 or older in the selected wedding. The guest identifier is required. Results return the saved guest details, including cleared values. This tool cannot change age bands, guest notes or dietary details. Requires sign-in and an Aisle membership.
  • update_my_wedding — Updates supplied wedding settings and can publish or unpublish the guest site. Omitted fields remain unchanged; nullable dates, location, venue and display name can be cleared. Partner names cannot be empty. Results identify saved changes with their previous values, every saved setting, the resulting couple display name and site address. Requires sign-in and an Aisle membership.

Data as of 2026-10-12T05:06:41+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections