Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Aisle is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
43
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Find wedding venues and vendors, estimate costs, and manage guests, events and wedding details.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aisle-mcp https://aisle.wedding/api/claude/mcp
# 2 — ask your agent for something these tools do
# search_venues, get_venue_details, list_venue_countries and 40 more
Aisle costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AIAll 1 server
aisle1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http aisle-mcp https://aisle.wedding/api/claude/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
43 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 bookin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Results per page, from 1 to 50 (default 50). |
| offset | integer | no | Number of results to skip; nextOffset from the previous page continues the result set. |
| summary | boolean | no | Return compact comparison fields without descriptions and images (default false). |
| country | string | no | Country name (e.g. "Italy", "Mexico"). A two-letter ISO code ("GR") or the country's own name ("Italia", "España") also works; appliedFilters.country gives the English name matched. |
| type | string | no | Venue type filter |
| capacity_min | integer | no | Lower end of your guest range. Matches venues with a known capacityMax at least this large; unknown capacity is excluded. |
| capacity_max | integer | no | Upper end of your guest range. Matches venues with a known capacityMin no larger than this; unknown capacity is excluded. |
| price_range | string | no | Price range filter: $ (budget) to $$$$ (luxury) |
| exclude_unverified_imports | boolean | no | Leave out unverified imported listings (descriptionStatus "unverified_import"), which carry no description and usually no capacity or price. Default false. |
| include_unknown_capacity | boolean | no | With capacity_min or capacity_max, also keep venues whose capacity is unknown (null) instead of leaving them out. Most imported listings have no known capacity. Default false. |
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 estimates are the ones the venue page shows, so a response gives one price for the venue and names any older estimate it left out. An estimators block names the d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Unique slug identifying a published Aisle venue. |
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.
No parameter schema on file.
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 Ai
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Results per page, from 1 to 50 (default 50). |
| offset | integer | no | Number of results to skip; nextOffset from the previous page continues the result set. |
| summary | boolean | no | Return compact comparison fields without descriptions and images (default false). |
| category | string | no | Vendor category filter, fuzzy-matched. One of: photographer, videographer, florist, caterer, dj, band, planner, coordinator, hair_makeup, cake_bakery, officiant, rentals_decor, stationery, transportat |
| location | string | no | Location slug filter (e.g. "austin-tx", "london-uk") |
| price_range | string | no | Price range filter: $ (budget) to $$$$ (luxury). Matches only listings whose vendor gave a band; generated listings have none. |
| min_rating | number | no | Only vendors with at least this Google rating, out of 5. Unrated vendors are left out. |
| min_reviews | integer | no | Only vendors with at least this many Google reviews. |
| sort | string | no | Result order: name (default), rating (highest first, ties broken by review count) or reviews (most reviewed first). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Unique slug identifying a published Aisle vendor. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| location | string | no | Location slug to filter vendor counts (e.g. "austin-tx") |
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| guest_count | integer | no | Total number of wedding guests |
| destination | string | no | Place slug for a destination or a country in Aisle’s wedding cost index, such as amalfi-coast, tuscany, santorini, italy or mexico. A destination without a row of its own, such as tulum or bali, is pr |
| country | string | no | Country name, used when no destination slug is given. Priced from that country as a whole. |
| style | string | no | Wedding style tier (default: mid-range) |
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. Each priced group gives a typical figure and a low-to-high range. Partial totals include only priced groups; unpriced guests and unsupported origins are reported separately. The ur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | no | Destination slug. Supported: algarve, amalfi-coast, argentina, aruba, aspen, bahamas, bali, barbados, barcelona, bermuda, cabo, cancun, cape-town, capri, charleston, cinque-terre, colombia, costa-rica |
| groups | array | no | Guest groups by departure city |
| nights | integer | no | Nights in the room, 1 to 30. Defaults to the destination's typical stay, shown as typicalStayNights on each group. |
| guests_per_room | integer | no | Guests sharing each room, 1 to 4. Defaults to 1, a private room per guest; 2 prices couples sharing. |
Returns a destination wedding planning timeline organized by months before the wedding, from venue planning through day-of logistics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| months_out | integer | no | Months until the wedding day (filters to show only relevant tasks) |
Returns a destination wedding packing list by climate and role, covering clothing, weather essentials, travel documents and practical supplies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| climate | string | no | Destination climate type (default: tropical) |
| role | string | no | Your role at the wedding (default: guest) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| months_out | number | no | Months until the wedding, returns only phases due within this window |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| guest_count | integer | no | Total number of wedding guests |
| non_drinkers | integer | no | Guests in guest_count who will not drink alcohol (default: 0). The bar and the toast are sized for the rest. |
| hours | integer | no | Hours of open bar (default: 5) |
| crowd | string | no | How much the crowd drinks (default: average) |
| mix | string | no | Bar mix across wine, beer, and spirits (default: balanced) |
| champagne_toast | boolean | no | Whether the estimate includes one flute of champagne per guest for a toast. Default: true. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ceremony_time | string | no | Ceremony start time, 24-hour ("16:00") or "4pm" / "4:30 PM" style; a bare hour with no am/pm is read as PM |
| first_look | boolean | no | Whether the couple does a first look before the ceremony (default: true) |
| reception_hours | no | Length of cocktail hour + reception in hours: 4, 5, or 6 (default: 5) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dress_code | string | no | Optional dress code name, matched approximately. An absent value returns the available codes. |
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, not obligations. This tool does not transfer money.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| total_budget | number | no | Total wedding budget in USD |
| model | string | no | Contribution model to split by (default: traditional) |
Generates deduplicated wedding hashtag suggestions from partner names, surnames, year and place, ordered by a deterministic score. Suggestions are not registrations or availability checks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first_name_a | string | no | One partner’s first name (e.g. "Maya") |
| last_name_a | string | no | That partner’s last name, classics build on this surname |
| first_name_b | string | no | The other partner’s first name |
| last_name_b | string | no | The other partner’s last name, adds puns, blends, and couple variants |
| year | integer | no | Wedding year for dated variants (e.g. 2027) |
| place | string | no | Wedding place for location variants (e.g. "Amalfi") |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scenario | string | no | Hosting-situation key. An absent value returns the available scenarios and formality options. |
| formality | string | no | Register key: formal, modern, casual, or playful |
| couple_a_name | string | no | One partner’s full name |
| couple_b_name | string | no | The other partner’s full name |
| host_names | string | no | Host names for scenarios that include hosts. Two hosting parties are separated by " / ". |
| hosts_child | string | no | Partner whose parents are hosting. Defaults to couple_b for grooms-parents and couple_a for brides-parents or divorced-parents. Partner names never determine parentage. |
| child_relationship | string | no | Relationship word for the hosts’ child. Defaults to child for divorced-parents, daughter for brides-parents and son for grooms-parents. |
| date | string | no | Date as it should read, e.g. "Saturday, the twelfth of June" |
| time | string | no | Time as it should read, e.g. "at four o’clock in the afternoon" |
| venue_name | string | no | Venue name |
| venue_location | string | no | Venue town and country |
| reception_note | string | no | Optional final line, e.g. "Reception to follow" |
| worship_space | boolean | no | Formal register: is the ceremony in a house of worship? |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relationship | string | no | Relationship to the couple: coworker, acquaintance, friend, close-friend, family or immediate-family. An absent value returns the available options. |
| party | string | no | Who attends: solo (default), couple, or family |
| travel | string | no | local (default), domestic-travel, or destination |
| in_wedding_party | boolean | no | Is the giver in the wedding party? |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Search query keywords (e.g. "legal requirements Italy", "budget tips", "what to wear") |
| max_per_guide | integer | no | How many sections one guide may hold among the 10 results (default 3). 1 gives one entry per guide; 10 ranks sections with no per-guide limit. |
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 with multiple weddings are asked which to use. Creates a private preview with no membership purchase, site publication, partner invitations or marketing-email e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| partner1_name | string | yes | First partner’s chosen name. |
| partner2_name | string | yes | Second partner’s chosen name. |
| wedding_date | string | no | Wedding date as YYYY-MM-DD. Omit when undecided. |
| location | string | no | Chosen wedding location. Omit when undecided. |
| venue_name | string | no | Booked venue name. Omit if the couple has not booked a venue. |
| confirmed | boolean | yes | True only after the couple confirms creating their wedding with these details. |
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 place. Access is limited to weddings the account can manage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| partner1_name | string | no | First partner name. Cannot be emptied, only replaced |
| partner2_name | string | no | Second partner name. Cannot be emptied, only replaced |
| couple_display_name | no | Custom display name for the couple. Null restores the combined partner names. A custom value remains unchanged when individual partner names change. | |
| wedding_date | no | Wedding date as a calendar day, YYYY-MM-DD, with no time and no zone, or null to clear it | |
| wedding_end_date | no | Wedding end date as a calendar day, YYYY-MM-DD, with no time and no zone, or null to clear it | |
| location | no | Wedding location, or null to clear it | |
| venue_name | no | Venue name, or null to clear it | |
| is_published | boolean | no | Guest-site visibility. True publishes the site at its address; false returns it to a private draft and hides it from guests, including those with an existing link. |
| room_selection_mode | string | no | Legacy bulk room choice: sets the wedding fallback and clears every property override, even when the supplied value matches the current wedding setting. Individual Hosted properties have their own roo |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| address | string | yes | The new address, without the aisle.wedding/ in front of it, for example maya-and-theo |
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 filterin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| rsvp_status | no | Filter by RSVP status, one status or a list such as ["pending", "maybe"] for everyone yet to confirm. | |
| language | string | no | Filter by a language name or code, such as Spanish or es. Empty string selects guests with no recorded language. Supported languages: English (en), Spanish (es), French (fr), Italian (it), German (de) |
| search | string | no | Search guests by name. A first name, a last name, or the whole name all match, and accents are ignored, so Ines finds Inês. |
| sort | string | no | Order of the guests. "name" (the default) is last name then first. "recently_updated", "recently_responded" and "recently_added" put the newest first, by updatedAt, rsvpRespondedAt and createdAt; gues |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| guest_id | string | yes | Identifier of a guest in the selected wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| first_name | string | yes | Guest first name |
| last_name | string | yes | Guest last name |
| phone | string | no | Guest phone number, including + and its country code |
| string | no | Optional guest email address. | |
| age_band | string | yes | Explicit confirmation that the guest is 13 or older, obtained before their name or contact details. Other age bands are ineligible. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| guest_id | string | yes | Identifier of a guest in the selected wedding. |
| first_name | string | no | Updated first name |
| last_name | string | no | Updated last name |
| string | no | Updated email address. Empty string clears it. | |
| phone | string | no | Updated phone number, including + and its country code. Empty string clears it. |
| rsvp_status | string | no | RSVP status |
| broadcast_channel | string | no | How this guest asked to be reached by messages sent to everyone: 'email' for email only, 'sms' for text only, 'either' for no preference. |
| preferred_transport | string | no | Which wire a text to this guest takes. 'sms' reaches US and Canadian numbers only; 'whatsapp' reaches any number and is the answer for a guest abroad. The guest can also choose on the wedding site. |
| language | string | no | Which language this guest reads. A language name ("Spanish") or a code ("es", "pt"); both store the same value. Decides the language their guest site opens in, and which version of a message they get. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| guest_id | string | yes | Identifier of the guest to remove from the selected wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| type | no | Filter by event type, one type or a list such as ["ceremony", "reception"]. | |
| from | string | no | First day to include, as YYYY-MM-DD in the wedding's time zone. |
| to | string | no | Last day to include, as YYYY-MM-DD in the wedding's time zone. |
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 other-wedding events return the same not-found result. Requires sign-in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| event_id | string | yes | Identifier of an event in the selected wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| name | string | yes | Event name |
| type | string | no | Event type |
| date | string | yes | Event start. A time with no offset, such as 2027-06-12T18:00, is the wedding's local time; one ending in Z or an offset is that exact instant. |
| end_time | string | no | Event end time, read the same way as date. |
| venue_name | string | no | Venue name for this event |
| venue_address | string | no | Venue address |
| dress_code | string | no | Dress code (e.g. Black Tie, Smart Casual) |
| description | string | no | Event description |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| event_id | string | yes | Identifier of the event to update in the selected wedding. |
| name | string | no | Event name |
| type | string | no | Event type |
| date | string | no | Event start. A time with no offset, such as 2027-06-12T18:00, is the wedding's local time; one ending in Z or an offset is that exact instant. |
| end_time | no | Event end time, read the same way as date., or null to clear it | |
| venue_name | no | Venue name for this event, or null to clear it | |
| venue_address | no | Venue address, or null to clear it | |
| dress_code | no | Dress code (e.g. Black Tie, Smart Casual), or null to clear it | |
| description | no | Event description, or null to clear it |
Removes an identified event from the selected wedding and returns the removed event's id and name. Requires sign-in and an Aisle membership.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| event_id | string | yes | Identifier of the event to remove from the selected wedding. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
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-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| property_id | string | no | Identifier of a property in the selected wedding. |
| property_name | string | no | Exact property name, ignoring case and surrounding spaces. Duplicate names require a property identifier. |
| room_selection_mode | yes | Property room choice: couple_assigned means the couple assigns rooms; guest_choice means guests choose available rooms. Null clears the override and follows the legacy wedding setting. A non-null choi |
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, capacity, status, stay details, stored price and deposit overrides in property order. Guest assignments and occupant identities are excluded. Requires sign-in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
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, removed and other-wedding rooms return the same not-found result. Guest assignments and occupant identities are excluded. Requires sign-in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| accommodation_id | string | yes | Identifier of a room in the selected wedding. |
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 names no place in the wedding returns a not-found result. The new room has no payment requirement. Results return the saved room and its place's id and name, and s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| property_id | string | no | Identifier of a place already in the selected wedding, as an alternative to property_name. |
| property_name | string | no | The property this room belongs to, e.g. "Castel Fragsburg". A name no place has starts a new place. Either this or property_id. |
| room_name | string | yes | The room, e.g. "Garden Suite" |
| room_type | string | no | e.g. "Double", "Suite" |
| description | string | no | Room description |
| capacity | number | no | How many it sleeps |
| check_in_date | string | no | Check-in date (ISO format) |
| check_out_date | string | no | Check-out date (ISO format) |
| check_in_time | string | no | e.g. 3:00 PM |
| check_out_time | string | no | e.g. 11:00 AM |
| check_in_notes | string | no | Check-in notes |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| accommodation_id | string | yes | Identifier of the room to update in the selected wedding. |
| room_name | string | no | The room name |
| room_type | no | e.g. "Double", "Suite", or null to clear it | |
| description | no | Room description, or null to clear it | |
| capacity | number | no | How many it sleeps |
| check_in_date | no | Check-in date (ISO format), or null to clear it | |
| check_out_date | no | Check-out date (ISO format), or null to clear it | |
| check_in_time | no | e.g. 3:00 PM, or null to clear it | |
| check_out_time | no | e.g. 11:00 AM, or null to clear it | |
| check_in_notes | no | Check-in notes, or null to clear it | |
| status | string | no | unavailable takes the room out of the block |
| requires_payment | boolean | no | Whether guests pay for this room |
| price_unit | string | no | What the amount buys |
| price_amount | no | The rate, or null to clear it, or 0 to make it free | |
| deposit_unit | string | no | How the deposit is stated: "amount" for a flat sum, "percent" for a share of whatever the room comes to |
| deposit_amount | no | What guests pay up front, with the rest due by balance_due_date. Null clears the schedule so the room is paid whole; 0 takes this room off a schedule its property sets. | |
| deposit_due_date | no | YYYY-MM-DD, the day the deposit is due. Without it the guest site says the deposit is due now. A date after balance_due_date is dropped. | |
| balance_due_date | no | YYYY-MM-DD, the day payment is due. Beside a deposit it dates the rest; on a room with no deposit it dates the whole price. Without it the room still charges, but nothing chases it. |
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 o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| accommodation_id | string | yes | Identifier of the room to remove from the selected wedding. |
| remove_empty_place | boolean | no | When true, also removes the room’s place if it has no other rooms or retained room history. Defaults to false, which keeps the place. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| place_ids | array | no | Complete list of property ids from the selected wedding’s places list, in the intended display order. Provide this or place_names. |
| place_names | array | no | Complete list of property names in the selected wedding, in the intended display order. Provide this or place_ids. |
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 lists which were removed and which kept, with the reason. A dry run reports the same without removing anything. This removes any recommendation or booking link
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
| place_id | string | no | Identifier of the empty property to remove, from the selected wedding’s places list. Provide this or place_ids. |
| place_ids | array | no | Identifiers of several empty properties to remove, from the selected wedding’s places list. Only these are considered. Provide this or place_id. |
| dry_run | boolean | no | When true, reports which of the named places would be removed and which kept, with reasons, and removes nothing. Defaults to false. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wedding_id | string | no | Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Aisle or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Aisle can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.