Enable MCP Server: Turns the server on and allows authorized external AI agents to access your account. Disabling it revokes all active tokens and disconnects every connected agent, so connected services must re-authenticate before they can reconnect.

Filter Personally Identifiable Information (PII): On by default. Sensitive information such as email addresses, phone numbers, and physical addresses is redacted from tool responses, and guest names are masked. Payment card numbers, SSNs, and credentials are always stripped, regardless of this setting.

Enable Write Tools: Off by default. Required for every tool that creates, changes, or removes data, including bookings, inquiries, replies, cancellations, calendar blocks, housekeeping assignments, reservation services, recorded refunds, payment requests, automated trigger settings, and work orders (including their photos and expenses).

Enable Message Access: Off by default. Required for tools that read guest conversations or inquiries. Sending a reply also requires Enable Write Tools.

Server URL: Shown on the Settings page and ready to copy.

Transport: Streamable HTTP

Authentication: OAuth 2.0

reservation_list: Retrieve reservations across your portfolio. By default it returns current and upcoming stays, soonest arrival first. Date filters let you look at past stays or reservations created in a given range. Cancelled reservations are excluded unless requested.

reservation_retrieve: Retrieve detailed information about a specific reservation, including guest visible invoice notes when your user is allowed to view them.

reservation_quote: Calculate pricing for a prospective stay. Read only; nothing is saved.

reservation_draft (write): Step 1 of booking. Creates a reservation in draft state, prices the stay, attaches an existing guest or creates a new one, and holds the reservation. Returns an error if the dates are unavailable.

reservation_book (write, confirm): Step 2 of booking. Confirms a draft reservation into a live, unpaid reservation and blocks the dates on the calendar. The AI must present the total and dates and receive your approval before confirming. Payment is collected separately through Lodgix.

inquiry_book (write, confirm): Books an existing inquiry directly. It confirms the inquiry's quote, links the inquiry to the new reservation, and keeps the same conversation thread, just like booking from the Lodgix inbox. This is the preferred path when an inquiry already exists.

render_quote_confirm: Displays the booking confirmation card, including the price summary and Confirm button, for either an inquiry or a draft reservation. Nothing is booked until you click Confirm.

reservation_cancel_preview: Shows what cancelling a reservation would look like: the amount paid, the cancellation fee and refund suggested by the reservation's cancellation policy, and the available refund methods. It also reports whether the reservation can be cancelled through MCP and why not. Changes nothing.

reservation_cancel (write, confirm): Cancels a direct (Lodgix) or Vrbo reservation, just like the Lodgix Cancel Reservation action. It keeps the cancellation fee, records the refund, frees the dates, cancels travel insurance, and runs your cancellation triggers (which may email the guest). This cannot be undone. Vrbo bookings show a partner fee warning first. Airbnb, Booking.com, and NextPax bookings must be cancelled on the channel instead.

reservation_refund_record (write, confirm): Records a refund on a reservation's invoice, just like the Record Refund action in Lodgix. It lowers the paid amount, updates the reservation status, and runs refund triggers.

payment_issue_list: Lists reservations with a failed or overdue guest payment. Failed payments match the Failed Transactions report, and overdue balances match the dashboard Balances Due list (Airbnb reservations are excluded because Airbnb collects payment). Requires permission to view guest balances and transactions.

payment_request_send (write, confirm): Emails the guest a payment request with a secure pay link, using your default payment request email template with an optional personal message. The email goes to the guest email on the reservation and cannot be unsent. The guest pays on the Lodgix pay page; this tool does not charge a card itself. Requires the Credit Card online payment method and a verified account email. Not available for Airbnb or Booking.com reservations, or for cancelled reservations, quotes, and blocks.

property_service_list: Lists the services (extras such as a boat rental, canoe, or firewood) set up for a property, including internal services.

reservation_service_add (write): Adds a service to a reservation's invoice and recalculates taxes, discounts, totals, and the balance. It does not email the guest or charge anything.

reservation_service_update (write): Changes the quantity or unit price of a service already on a reservation and recalculates the totals.

reservation_service_remove (write, confirm): Removes a service from a reservation's invoice and recalculates the totals. Nothing is refunded or charged.

reservation_trigger_list: Lists the automated triggers (scheduled emails, texts, and other actions) that apply to a reservation, the same information shown on the reservation's Triggers tab. Shows whether each trigger is active, whether it can still be changed, whether it was already sent, and whether a send is queued.

reservation_trigger_set_enabled (write): Turns one automated trigger on or off for a single reservation without changing the trigger itself. For example, you can skip the check in instructions email for one booking. Turning off a trigger does not stop a send that is already queued; the AI will warn you when that happens.

block_list: Lists calendar blocks (owner stays, maintenance, and lockout blocks created by linked properties) that overlap a date range. Guest reservations are not included.

block_create (write): Blocks dates on a property's calendar so they cannot be booked. It works like blocking dates on the Lodgix booking calendar, so linked lockout properties are blocked too and your channels pick up the change automatically. Refused if the dates overlap an existing reservation or block.

block_delete (write, confirm): Removes a calendar block so the dates can be booked again, including the lockout blocks it created on linked properties. Lockout blocks that belong to another reservation cannot be deleted directly.

availability_search: Search flexible availability to find properties with open booking windows. Search by month or around a target date, set minimum and maximum stay lengths, and filter by guests, bedrooms, weekends, or specific properties. Returns open windows and nightly rates. Properties that require a longer minimum stay are still returned at the length they allow.

property_multi_availability: Check exact dates across multiple properties at once.

property_availability_arrays: Retrieve structured availability data for planning and scheduling.

inquiry_list (inbox): List guest inquiries, newest first, with filters for guest name, email, property, or stay dates. The needs_response filter returns actionable inquiries where the guest messaged last and is waiting for a reply.

inquiry_retrieve (inbox): Retrieve the full details of an inquiry, including the original message.

inquiry_create (write): Create a new inquiry or lead, such as for a guest who called or emailed. It is recorded like an inquiry submitted through your Lodgix website and enters the normal inquiry workflow.

inquiry_update_dates (write, inbox): Change an inquiry's check in and check out dates. If the inquiry has a quote, the quote is moved one day at a time using the same flow as the Lodgix inbox, validating conflicts and booking rules and repricing at each step. If any step is blocked, nothing changes and the blocking reason is returned. Booked inquiries cannot be edited, and the guest count cannot be changed.

message_list (inbox): Read the message history for a guest conversation using either a reservation ID or inquiry ID. Returns the thread oldest first with the full body of each message and can be filtered by sender type, including guests, PMs, owners, or the system.

message_send (write, inbox): Send a reply on a guest conversation or save an internal note. Guest replies are delivered through the guest's booking channel and cannot be unsent. The AI is instructed to show the exact message and request confirmation before sending. The result reports whether the message was sent, saved as a note, held for review, or failed.

housekeeping_job_list: Lists housekeeping turnovers (departures) in a date range, including turnovers with no housekeeper assigned. Flags same day turnovers (the next guest arrives on the clean date) and housekeeper conflicts (one housekeeper with two or more same day turnovers). Cleaning Staff users see only their own jobs plus unassigned turnovers.

housekeeping_job_retrieve: Full detail for one turnover: assigned housekeeper, clean date, task type, status, instructions and comments, eligible housekeepers, damage notice with private photo links (valid for one hour), arrival and departure housekeeping notes, and recent change history.

housekeeper_list: Lists your active housekeepers (Cleaning Staff team members) and the properties each is assigned to by default.

housekeeping_job_assign (write): Assigns or reassigns the housekeeper for an upcoming turnover, creating the housekeeping job if needed.

housekeeping_job_update (write): Changes fields on an existing housekeeping job, such as instructions, comments, clean date, task type, or status.

housekeeping_job_unassign (write, confirm): Removes the housekeeping job from a turnover so it shows as unassigned again. The job's clean date, status, instructions, and comments are deleted with it.

property_list: Retrieve a list of properties in your portfolio. Active properties are returned by default, with an option to include disabled properties.

property_retrieve: Retrieve detailed information about a specific property.

guest_list: Search and retrieve guests in your guest database, with filters for email and name.

guest_retrieve: Retrieve detailed information about a specific guest.

guest_status_list: Retrieve the available guest status values.

work_order_list: View work orders.

work_order_retrieve: Retrieve details about a specific work order.

work_order_create (write): Create work orders with support for:

work_order_update (write): Partially update any work order field.

work_order_photo_list: List photos attached to a work order.

work_order_photo_create (write): Attach photos to work orders. Uploaded photos must be 10 MB or smaller.

work_order_photo_delete (write): Remove a photo from a work order.

work_order_expense_material_list: List expense and material line items on a work order.

work_order_expense_material_create (write): Add expense or material line items.

work_order_expense_material_update (write): Update an existing expense or material entry.

work_order_expense_material_delete (write): Remove an expense or material entry.

work_order_vendor_list / work_order_vendor_retrieve: Look up available vendors.

work_order_job_type_list / work_order_job_type_retrieve: Look up available job types.

work_order_expense_account_list / work_order_expense_account_retrieve: Look up expense accounts.

work_order_status_list: List valid statuses: Open, Escalated, Closed, and Cancelled.

work_order_priority_list: List valid priorities: Critical, Urgent, High, Medium, Low, and Project.

owner_list / owner_retrieve: Retrieve information about property owners.

team_member_list / team_member_retrieve: Retrieve information about team members.

Granted scopes: When you connect an agent, you approve a specific set of scopes: reservation read and write, guest read and write, work order read and write, owner read, team member read, inbox read and write, and calendar read and write. A tool only runs if its required scope was granted.

Live permission checks: Tools re-check the connected user's Lodgix permissions on every call, so changes take effect immediately, even for tokens issued earlier. For example, viewing or editing reservations, cancelling reservations, accessing the booking calendar, viewing team members, and viewing guest balances each require the matching Lodgix permission. Inbox tools also re-check the user's inbox access and permission to reply to guests. Property owners cannot use inbox tools. A user who can post internal notes but cannot reply to guests can still record notes.

Confirmation before sensitive actions: Confirming a booking, sending a guest message, cancelling a reservation, recording a refund, sending a payment request, removing a service, deleting a calendar block, and unassigning a housekeeper all require an explicit confirmation step. The tools refuse to proceed without it.

No money moves through MCP: No tool charges a card or issues a refund. Payment requests send the guest a secure pay link, and refunds are recorded in Lodgix only.

Audit trail: Every tool call, whether allowed or denied, is recorded in the Audit Log.