The agent-pricing path is what separates this from a consumer booking tool: availability comes back with your rate, and the quote call spells out commission before anything is confirmed. Two things to settle before wiring it up. Payments split into a manual mode where you take the money yourself and the booking sits pending, and a processed mode that runs the card through Rezdy — different obligations, same tools. And there is a staging environment: use it while you are learning the booking calls, because the production ones create real reservations.
An MCP server for the Rezdy Agent API, which is the agent-side view of the Rezdy tour and activity marketplace. It covers the whole agent workflow: find a supplier's product, check what is available and what it costs you after commission, quote it, book it, and keep the customer on file for next time.
- Marketplace search across all suppliers with filters for location, price range, category, supplier and tags, plus full product detail and pickup locations — `rezdy_agent_search_products`, `rezdy_agent_get_product`, `rezdy_agent_get_product_pickups`
- Availability with agent pricing rather than retail, so commission is visible before you quote — `rezdy_agent_search_availability`
- The booking lifecycle end to end: a quote with commission detail, a confirmed booking, retrieval, updates and cancellation — `rezdy_agent_quote_booking`, `rezdy_agent_create_booking`, `rezdy_agent_get_booking`, `rezdy_agent_update_booking`, `rezdy_agent_cancel_booking`
- Your own customer database, separate from the suppliers' — search it, create profiles, open one — `rezdy_agent_search_customers`, `rezdy_agent_create_customer`, `rezdy_agent_get_customer`
- Marketplace reference data for narrowing a search: categories, locations and suppliers — `rezdy_agent_get_categories`, `rezdy_agent_get_locations`, `rezdy_agent_get_suppliers`
- Booking modes the marketplace actually uses, including no-date and date-enquiry products alongside inventoried ones, with custom fields, participant management and promotional codes
- Automatic rate limiting at 100 calls per minute with queuing, so a burst of searches does not trip the API
A Rezdy Agent account and an Agent API key created under Settings → API Keys. The key is not read from the environment: you pass it, along with a staging or production choice, through a configuration tool at the start of a session — `rezdy_agent_configure`. Node.js; clone, `npm install`, `npm run build`, then point your client at the built entry with node. A Docker path is also documented, taking `REZDY_API_KEY` and `REZDY_ENVIRONMENT` from a `.env` file. The package is `rezdy-agent-mcp` (1.0.0 in package.json).
Run a container — pull the image and point your client at it