rezdy_agent_configureLABSCO SUMMARY
Quote first — the commission is in the quote, not the search.
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.
What it is
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.
What you get
- 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
Requirements
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).
Setup effort
Build from source — git clone https://github.com/jezweb/rezdy-agent-mcp.git
USE CASES
01
Finding something for a client with a budget and a place
Search the marketplace filtered by location, price band and category, then open the products that fit and check their pickup points.
02
Quoting a trip before committing to it
Check availability for the dates and party size at agent pricing, then generate a quote showing the commission you keep.
03
Booking a repeat customer
Search your own customer database for the profile rather than re-entering their details, then create the booking against it.
04
Handling a change after the fact
Open the booking, update the details that changed, or cancel it — from the conversation where the customer told you.
16 tools
Listed in project docs. Your client may show a different list.
rezdy_agent_search_productsrezdy_agent_get_productrezdy_agent_get_product_pickupsrezdy_agent_search_availabilityrezdy_agent_quote_bookingrezdy_agent_create_bookingrezdy_agent_get_bookingrezdy_agent_update_bookingrezdy_agent_cancel_bookingrezdy_agent_search_customersrezdy_agent_create_customerrezdy_agent_get_customerrezdy_agent_get_categoriesrezdy_agent_get_locationsrezdy_agent_get_suppliersBEFORE YOU INSTALL
What to know first
Tools you get
16 tools named in the project's documentation.
Requires
Node.js and npm
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/jezweb/rezdy-agent-mcp.git
cd rezdy-agent-mcp
npm install
npm run buildMCP Clients
Claude Desktop, Cursor, Roo Code
JSON
{
"mcpServers": {
"rezdy-agent": {
"command": "node",
"args": [
"<YOUR_PATH_TO_REZDY_AGENT_MCP>/build/index.js"
]
}
}
}None of these configurations sets your Rezdy key. After connecting, ask the assistant to run rezdy_agent_configure with your Agent API key (Settings → API Keys in your Rezdy Agent account) and the environment, staging or production.
