Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Lodgify MCP Server list all my properties and their current bookings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server for the Lodgify vacation rental API. It exposes tools for managing properties, bookings and calendar data.
Install dependencies with uv and run the server with uvx:
export LODGIFY_API_KEY=your_api_key
uvx lodgify-mcp-serverTo run from source:
git clone https://github.com/fast-transients/lodgify-mcp-server.git
cd lodgify-mcp-server
uv sync
export LODGIFY_API_KEY=your_api_key
uv run python entrypoint.pyRelated MCP server: Hostaway-mcp
Add this block to your Claude Desktop configuration (see examples in the examples/ folder):
{
"mcpServers": {
"lodgify": {
"command": "uvx",
"args": ["lodgify-mcp-server"],
"env": {
"LODGIFY_API_KEY": "your_api_key"
}
}
}
}Properties: get_properties, get_property_by_id
Bookings: get_bookings, get_booking_by_id, create_booking, update_booking_status
Calendar: get_calendar
Ensure the LODGIFY_API_KEY environment variable is set.
Getting spawn uvx ENOENT? Install uv from astral.sh/uv and restart your shell.
After syncing dependencies, run pip-audit to check for known vulnerabilities. The uv.lock file pins starlette 0.47.0 to address upstream advisories.
See CONTRIBUTING.md for development setup and testing instructions.
Create a new booking.
Args:
property_id: The property ID for the booking
room_type_id: The room type ID within the property
arrival: Arrival date (YYYY-MM-DD)
departure: Departure date (YYYY-MM-DD)
guest_name: Guest's full name
guest_email: Guest's email address
guest_phone: Guest's phone number
guest_country_code: Guest's country code (e.g., "US", "CA")
people: Number of people (default: 2)
total: Total booking amount (default: 0.0)
currency_code: Currency code (default: "USD")
status: Booking status (default: "Booked")
source_text: Source description (default: "MCP API")
Inputs: property_id (required), room_type_id (required), arrival (required), departure (required), +9 more.
Get detailed information about a specific booking.
Args:
booking_id: The unique ID of the booking
Inputs: booking_id (required).
Get bookings with optional filtering.
Args:
size: Maximum number of bookings to return
page: Number of page to get
property_id: Filter by specific property ID
status: Filter by booking status (e.g., "Booked", "Cancelled")
start_date: Filter bookings from this date (YYYY-MM-DD)
end_date: Filter bookings until this date (YYYY-MM-DD)
Inputs: size, page, property_id, status, +2 more.
Get calendar/availability information for a property.
Args:
property_id: The property ID
room_type_id: Optional room type ID within the property
start_date: Start date for calendar (YYYY-MM-DD)
end_date: End date for calendar (YYYY-MM-DD)
Inputs: property_id (required), room_type_id, start_date, end_date.
Get occupancy summary, average rental rate, and total revenue for a property
within a specified date range.
Args:
property_id: The property ID
start_date: Start date for analysis (YYYY-MM-DD)
end_date: End date for analysis (YYYY-MM-DD)
Inputs: property_id (required), start_date (required), end_date (required).
Get a list of properties with optional filtering.
Args:
limit: Maximum number of properties to return (default: 50)
offset: Number of properties to skip (default: 0)
status: Filter by property status (e.g., "Active", "Inactive")
Inputs: limit, offset, status.
Get detailed information about a specific property.
Args:
property_id: The unique ID of the property
Inputs: property_id (required).
Update the status of an existing booking.
Args:
booking_id: The unique ID of the booking
status: New status (e.g., "Booked", "Cancelled", "CheckedIn", "CheckedOut")
Inputs: booking_id (required), status (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools cover different aspects of the Lodgify domain: booking creation, retrieval, status updates, property management, calendar/availability, and occupancy analysis. There is no overlap in functionality between tools like get_booking_by_id, get_bookings, and update_booking_status.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is predictable: create_booking, get_booking_by_id, get_bookings, get_calendar, get_occupancy_summary, get_properties, get_property_by_id, update_booking_status. This consistency makes it easy for agents to understand and select the appropriate tool.
With 8 tools, this server is well-scoped for property management and booking operations. Each tool earns its place by covering essential CRUD operations for bookings and properties, plus additional utilities like calendar and occupancy analysis. The count is neither too thin nor too heavy for the domain.
The tool surface provides strong coverage for core booking and property management workflows, including create, read, and update operations. Minor gaps exist, such as no delete_booking or update_property tools, but agents can work around these with the available status updates and property retrieval. The inclusion of calendar and occupancy tools adds valuable domain-specific functionality.
Manage vacation rentals, bookings, calendars and operations with OAuth and action approvals.
Manage Hostaway listings, reservations, calendar, guest messages, reviews and tasks.
Manage OwnerRez properties, bookings, guests, quotes and inquiries.
Ask your AI about your Airbnb and VRBO listings, bookings, guest messages and reviews. Read-only.