Aisle is a remote MCP server that gives an AI agent 44 tools, among them add_my_accommodation, add_my_event, add_my_guest. It answers at https://aisle.wedding/api/claude/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 2 October 2026; the last check, on 17 November 2026, succeeded.
Find wedding venues and vendors, estimate costs, and manage guests, events and wedding details.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_my_accommodation | Adds an unpriced room under a property in the selected wedding. The property is named by the id of a place already in the wedding or by a name, which uses the place with that name or starts a new one; a room name is required. An id that nam Inputs: wedding_id, property_id, property_name, room_name, room_type, description |
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. Inputs: wedding_id, name, type, date, end_time, all_day |
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 g Inputs: wedding_id, first_name, last_name, title, phone, email |
create_my_wedding | Creates the signed-in couple’s first wedding after explicit confirmation, using both partner names and an optional date, location and venue. Unknown date and location may be omitted. Existing weddings are returned without changes; accounts Inputs: partner1_name, partner2_name, wedding_date, location, venue_name, confirmed |
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. Inputs: first_name_a, last_name_a, first_name_b, last_name_b, year, place |
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. Inputs: guest_count, non_drinkers, hours, crowd, mix, champagne_toast |
get_budget_estimate | Estimates a whole destination wedding budget in USD, EUR or GBP 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 coun Inputs: guest_count, destination, country, style, currency, ceremonies |
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 mone Inputs: relationship, party, travel, in_wedding_party |
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. Inputs: ceremony_time, first_look, reception_hours |
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. Inputs: dress_code |
get_guest_travel_estimate | Estimates round-trip flights and lodging in USD for guest groups departing from supported cities in the United States, Canada, the United Kingdom, Ireland and France. Stay length and guests per room can be set, and default to the destinatio Inputs: destination, groups, nights, guests_per_room |
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 lega Inputs: scenario, formality, couple_a_name, couple_b_name, host_names, hosts_child |
get_my_accommodation | Returns one identified room in the selected wedding, with its property, description, capacity, status, stay details and stored price and deposit overrides, plus its place's id, name, stored room-choice override and effective mode. Missing, Inputs: wedding_id, accommodation_id |
get_my_event | Returns one identified event in the selected wedding, with its name, type, date, time, venue, dress code and description, the ids of other events whose times overlap it, and the dress-code guide entry its dress code matches. Missing and oth Inputs: wedding_id, event_id |
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 unco Inputs: wedding_id, guest_id |
get_my_wedding | Returns the signed-in account's selected wedding details, including partner names, date, location and venue, the city and country picked in settings, and the destination to pass to the budget and guest travel estimates for the wedding's own Inputs: wedding_id |
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 ra Inputs: wedding_id |
get_packing_list | Returns a destination wedding packing list by climate and role, covering clothing, weather essentials, travel documents and practical supplies. Inputs: climate, role |
get_planning_timeline | Returns a destination wedding planning timeline organized by months before the wedding, from venue planning through day-of logistics. Inputs: months_out |
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 suppl Inputs: slug |
get_venue_details | Returns a published wedding venue by its slug, including photos, highlights, travel information, planning estimates and available sourced facts with provenance, with each price also given as numbers, its currency and what it is per. Cost es Inputs: slug |
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. Inputs: months_out |
get_who_pays_split | Calculates percentages and amounts for dividing a wedding budget among the couple and their families under a selected model, with each amount also given as a whole-dollar USD number. Traditional assignments describe etiquette conventions, n Inputs: total_budget, model |
list_my_accommodations | Lists the selected wedding's places, including empty places with ids, position, arrangement, active and archived room counts, whether each place can be removed, stored room-choice overrides and effective modes, plus room descriptions, capac Inputs: wedding_id |
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 e Inputs: wedding_id, type, from, to |
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, l Inputs: wedding_id, rsvp_status, language, search, sort |
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. Inputs: wedding_id |
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. Inputs: location |
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. |
place_my_guests_in_rooms | Places many guests in the selected wedding's rooms in one call, from a rule (reply, group, named guests, optionally limited to a place or rooms) or from a list of rooms and guests. Rooms are filled to their bed counts with each household ke Inputs: wedding_id, fill, assignments, set_rsvp_status, dry_run |
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 payme Inputs: wedding_id, accommodation_id, remove_empty_place |
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. Inputs: wedding_id, event_id |
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. Inputs: wedding_id, guest_id |
remove_my_place | Removes one or several identified empty places from the selected wedding and its property order, and returns the order that remains. The places list supplies their ids. With several, each place is removed or kept on its own, and the result Inputs: wedding_id, place_id, place_ids, dry_run |
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 Inputs: wedding_id, place_ids, place_names |
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. Inputs: query, max_per_guide |
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 gene Inputs: limit, offset, summary, category, location, price_range |
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; s Inputs: limit, offset, summary, country, type, capacity_min |
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 Inputs: wedding_id, property_id, property_name, room_selection_mode |
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 Inputs: wedding_id, address |
update_my_accommodation, update_my_event, update_my_guest, update_my_wedding
Every block below points at https://aisle.wedding/api/claude/mcp. Pick your client and copy.
claude mcp add --transport http aisle https://aisle.wedding/api/claude/mcp
{
"mcpServers": {
"aisle": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://aisle.wedding/api/claude/mcp"]
}
}
}{
"mcpServers": {
"aisle": {
"url": "https://aisle.wedding/api/claude/mcp"
}
}
}{
"servers": {
"aisle": {
"type": "http",
"url": "https://aisle.wedding/api/claude/mcp"
}
}
}{
"context_servers": {
"aisle": {
"url": "https://aisle.wedding/api/claude/mcp"
}
}
}{
"mcpServers": {
"aisle": {
"serverUrl": "https://aisle.wedding/api/claude/mcp"
}
}
}{
"mcpServers": {
"aisle": {
"url": "https://aisle.wedding/api/claude/mcp"
}
}
}name: Aisle
version: 0.0.1
schema: v1
mcpServers:
- name: Aisle
type: streamable-http
url: https://aisle.wedding/api/claude/mcp{
"mcpServers": {
"aisle": {
"httpUrl": "https://aisle.wedding/api/claude/mcp"
}
}
}{
"mcpServers": {
"aisle": {
"type": "http",
"url": "https://aisle.wedding/api/claude/mcp"
}
}
}{
"mcpServers": {
"aisle": {
"url": "https://aisle.wedding/api/claude/mcp"
}
}
}goose://extension?url=https%3A%2F%2Faisle.wedding%2Fapi%2Fclaude%2Fmcp&type=streamable_http&id=aisle&name=Aisle
It answered our last check on 17 November 2026 in 206 ms. Over 4 checks since 2 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by aisle.wedding and served from aisle.wedding, the vendor's own domain: https://aisle.wedding/api/claude/mcp.
44, as returned by the server's own tools/list on 20 November 2026: add_my_accommodation, add_my_event, add_my_guest, create_my_wedding, generate_wedding_hashtags, get_alcohol_estimate, get_budget_estimate, get_cash_gift_suggestion, and 36 more.
It answered our last check on 17 November 2026 in 206 ms. Over 4 checks since 2 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://aisle.wedding/api/claude/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: wedding.aisle. Endpoint host: aisle.wedding. ARD identifier: urn:air:wedding.aisle:mcp:aisle.
First indexed 2 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.