Rizerve MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port when TRANSPORT=http | 3000 |
| TRANSPORT | No | stdio for local MCP clients, http for remote access | stdio |
| RIZERVE_API_KEY | Yes | API key from Rizerve Dashboard → Integrations → API Access | |
| RIZERVE_API_URL | No | API base URL (change for staging/testing) | https://api.rizerve.io/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rizerve_list_propertiesA | List all properties owned by the authenticated account. This tool returns properties with full details including pricing (in cents), amenities, availability settings, and branding configuration. Args:
Returns: For JSON format: Paginated response with { data: Property[], meta: { total, page, limit } } For markdown format: Formatted list with property details Examples:
|
| rizerve_get_propertyA | Get a single property by its public slug. Args:
Returns: Full property object with all details. Examples:
Error Handling:
|
| rizerve_create_propertyC | Create a new property listing. Required fields: title, price_per_night (in cents). Optional: description, location, public_slug (auto-generated if omitted), bedrooms, bathrooms, max_guests, amenities, minimum_stay, check_in_time, check_out_time, extra_fee, extra_fee_type, theme_color, latitude, longitude, main_site_url. Args:
Returns: Created property object with generated id and public_slug. Examples:
|
| rizerve_update_propertyA | Update a property's details. Send only the fields you want to change — omitted fields are left unchanged. Args:
Examples:
|
| rizerve_delete_propertyA | Delete a property permanently. ⚠️ DESTRUCTIVE: This action cannot be undone. All bookings, availability data, and iCal feeds for this property will also be deleted. Args:
Examples:
|
| rizerve_list_bookingsA | List bookings across all properties with optional filters. Supports filtering by status, property, and date range. Results are paginated. Args:
Returns: Paginated booking list with full guest details, pricing, and status. Examples:
|
| rizerve_get_bookingA | Get a single booking by its UUID. Args:
Returns: Full booking object with guest details, dates, pricing, and status. Examples:
|
| rizerve_create_bookingA | Create a new booking for a property. Automatically blocks the calendar for the booked dates. Required: property_id, guest_name, check_in, check_out, total_price (in cents). Returns 409 conflict if dates overlap with existing bookings. Args:
Returns: Created booking object with status "pending". Examples:
|
| rizerve_update_booking_statusA | Update a booking's status. Valid transitions:
Cancelling unblocks the calendar dates. Confirming keeps them blocked. Args:
Examples:
|
| rizerve_get_availabilityA | Check availability for a property over a date range. Returns available/blocked dates with reasons. Also returns overall availability status (true/false) for the entire range. Args:
Returns: Availability data with total_nights, available_nights, blocked_dates, and overall available flag. Examples:
|
| rizerve_block_dateA | Block or unblock a specific date for a property. Use to mark dates as unavailable for maintenance, owner stays, or manual blocks. Args:
Examples:
|
| rizerve_batch_set_availabilityA | Set availability for multiple properties and date ranges at once. Efficient for bulk operations like blocking off-season dates or marking multi-property maintenance windows. Args:
Returns: Summary with number of ranges processed and total dates affected. Examples:
|
| rizerve_list_ical_feedsA | List external iCal feeds imported for a property. Shows feed URLs, sources (Airbnb, Booking.com, etc.), and last sync times. Args:
Returns: Array of iCal feed objects with sync status. Examples:
|
| rizerve_import_ical_feedA | Import an external iCal feed for auto-sync. The system will sync it within a few minutes. Use this to pull calendars from Airbnb, VRBO, Booking.com, etc. into Rizerve. Args:
Returns: Created feed object. Examples:
|
| rizerve_export_icalA | Get a property's public iCal feed URL for importing into OTAs (Airbnb, VRBO, Booking.com). This is the URL you give to external platforms so they can read Rizerve's calendar. Args:
Returns: Public iCal URL for the property. Examples:
|
| rizerve_delete_ical_feedA | Remove an imported iCal feed. Imported dates from this feed are cleared. Args:
Examples:
|
| rizerve_get_property_statsA | Get detailed statistics for a single property. Includes page views, bookings, conversion rate, revenue, average stay length, and occupancy rate. Args:
Returns: Property stats object with all metrics. Examples:
|
| rizerve_get_revenue_reportA | Get revenue report across all properties with breakdown by period or property. Args:
Returns: Total revenue with breakdown. Examples:
|
| rizerve_get_occupancy_reportA | Get occupancy rates across properties. Args:
Returns: Overall occupancy rate with per-property breakdown. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action. For example, rizerve_block_date and rizerve_batch_set_availability are clearly differentiated by scope (single vs. batch). The booking and property tools form clear CRUD sets with no overlap.
All tools follow the consistent pattern 'rizerve_verb_noun', using standard verbs like create, get, list, update, delete, block, import, export. No mixing of styles or ambiguous verbs.
19 tools is appropriate for a property management server, covering properties, bookings, availability, iCal feeds, reports, and stats without excessive granularity.
The tool set covers core CRUD for properties and bookings, plus availability management and reports. A minor gap is the lack of a tool to update booking details beyond status (e.g., dates, guest name).