Daytrip MCP server

What Daytrip is

Daytrip (https://daytrip.com) sells private, fixed-price, door-to-door car transfers between cities, airports, ports and resorts in 130+ countries across Europe, the Americas, Asia, Africa and Oceania. Every booking is a dedicated vehicle with a vetted local driver, never shared with strangers, and on intercity routes the traveler can add sightseeing stops along the way.

The MCP server lets an AI assistant search those transfers, quote a live price for a chosen vehicle and stops, and hand the traveler a link to finish the booking on daytrip.com. It is read-only from the traveler's point of view: nothing is reserved and nothing is charged until the traveler pays on the website. Day trips and hourly bookings are not searchable through it yet.

Connect


Server URL	`https://mcp.daytrip.com/mcp`
Transport	Streamable HTTP (MCP 2025-06-18). Send one JSON-RPC message per `POST`. A request gets a JSON response; an accepted notification (such as `notifications/initialized`) gets HTTP `202` with an empty body. The server is stateless, so `GET` and `DELETE` on the endpoint answer 405.
Authentication	None. Searching, quoting and the booking link need no sign-in, API key or header.
Server card	`https://mcp.daytrip.com/mcp/server-card` (also at `/.well-known/mcp/server-card.json` on this host and on daytrip.com)

Add it to Claude

Open Customize → Connectors in Claude (web or desktop), click Add, then Add custom connector. On a Team or Enterprise plan an owner adds it under Organization settings → Connectors instead, and members then click Connect.
Name it Daytrip, paste the server URL https://mcp.daytrip.com/mcp and click Continue.
Under Authentication choose No sign in. Leave Request headers empty: the public tools take no API key. Click Add.
The three tools below appear in the connector's tool list; no sign-in step follows.

In Claude Code:

claude mcp add --transport http daytrip https://mcp.daytrip.com/mcp

Any other MCP client that speaks Streamable HTTP connects the same way: the endpoint URL and no credentials.

Example prompts

"Find me a private transfer from Vienna to Budapest on 12 May, two adults, one child."
"How much is a sedan from Naples airport to Positano next Friday at 10, with a stop in Pompeii?"
"Give me a link to book the van option."

Tools

Every result is returned twice, as structuredContent and as the same JSON in a text block, preceded by a short plain-language summary. Each result carries a status; anything other than the success status also carries a code and a message. These outcomes are results, not errors: a tool call fails with isError only when something unexpected happened on the server.

Access class says what the tool does to Daytrip's data. Read-only tools change nothing. Write tools create data on Daytrip's side but never a booking or a charge.

`search_trips` Read-only

Search Daytrip transfers

Search Daytrip private door-to-door car transfers between two places (city to city, airport to city, …) and get bookable prices for every vehicle class.

Inputs

Field	Type		Description
`origin`	string	required	Pickup place as the customer said it: a city, airport, IATA code or "City, Country". To pick an ambiguous_location candidate, pass its label verbatim.
`destination`	string	required	Drop-off place, same rules as origin.
`departureAt`	string	required	Pickup date and time, ISO 8601. Without an offset it is local time at the pickup place (e.g. 2026-10-01T09:00); with an offset or Z it is converted to the pickup place's local time.
`adults`	integer	required	Number of adult passengers (the lead traveler counts as one).
`children`	integer	optional, default 0	Number of children (under 12).
`additionalLuggage`	integer	optional, default 0	Suitcases beyond one per passenger; each passenger already has one suitcase and one carry-on included.
`currency`	one of eur, usd, aud, cad, gbp, nzd, czk, mxn	optional	ISO 4217 code the customer prefers (eur, usd, gbp, …). Adds priceInRequestedCurrency and makes the checkout charge in it.
`locale`	one of en, es, de, fr, pt	optional, default "en"	Customer language (en, de, es, fr, pt). Used for the handover link.

Returns

status	Meaning
`ok`	One option per vehicle class with its price, capacity, duration and `expiresAt`, the resolved origin and destination, and `availableStops`, the sightseeing stops on the way with their extra cost. Prices are per vehicle, all-inclusive, and valid until `expiresAt`.
`ambiguous_location`	The origin or destination could mean several places; `candidates` lists them. Search again with the chosen candidate's label.
`location_not_found`	The place could not be resolved. Use a city, airport or IATA code.
`invalid_departure`	The date or time could not be read, or is in the past.
`route_not_available`	Daytrip does not serve that trip.
`price_unavailable`	Nothing could be priced for that date.

`get_quote` Read-only

Quote a Daytrip transfer

Price one search_trips option exactly as it will be booked: the chosen vehicle, the party and any stops.

Inputs

Field	Type		Description
`offerId`	string	required	offerId of the chosen search_trips option.
`vehicleType`	string	required	vehicle.type of the chosen search_trips option (a class identifier such as sedan or van).
`adults`	integer	required	Number of adult passengers, including the lead traveler.
`children`	integer	optional, default 0	Number of children.
`additionalLuggage`	integer	optional, default 0	Suitcases beyond one per passenger.
`currency`	one of eur, usd, aud, cad, gbp, nzd, czk, mxn	optional	ISO 4217 code to show the price in as well; use the one from search_trips.
`locale`	one of en, es, de, fr, pt	optional, default "en"	Language of the traveler's pages and emails (en, de, es, fr, pt).
`stops`	array of object	optional, default []	Sightseeing stops from the search's availableStops the customer wants to add, in any order.
`stops[].locationId`	string	required	locationId of an availableStops entry from search_trips.
`stops[].durationMinutes`	integer	optional	Time at the stop; defaults to the stop's defaultDurationMinutes.
`customStops`	array of object	optional, default []	Stops at places not in availableStops. The trip is then routed and priced through them, so the price will differ from the search.
`customStops[].place`	string	required	Free-text place, like origin/destination.
`customStops[].durationMinutes`	integer	required	Time at the stop.

Returns

status	Meaning
`quoted`	The total price and currency for the chosen vehicle, party and stops, what is included, when the traveler is charged, the cancellation policy with its free-cancellation deadline, and `expiresAt`. `previousPrice` is set when the price differs from the search option.
`offer_expired`	The search option is gone; search again.
`route_not_available`	The trip can no longer be priced.
`invalid_input`	The vehicle type or a stop does not belong to that offer; `message` says what to fix.

`get_booking_link` Write: creates a booking draft, never a booking or a charge

Prepare a Daytrip booking on daytrip.com (handover link)

Prepare a search_trips option on daytrip.com and return a link where the traveler finishes the booking themselves.

Inputs

Field	Type		Description
`offerId`	string	required	offerId of the chosen search_trips option.
`vehicleType`	string	required	vehicle.type of the chosen search_trips option (a class identifier such as sedan or van).
`adults`	integer	required	Number of adult passengers, including the lead traveler.
`children`	integer	optional, default 0	Number of children.
`additionalLuggage`	integer	optional, default 0	Suitcases beyond one per passenger.
`currency`	one of eur, usd, aud, cad, gbp, nzd, czk, mxn	optional	ISO 4217 code to show the price in as well; use the one from search_trips.
`locale`	one of en, es, de, fr, pt	optional, default "en"	Language of the traveler's pages and emails (en, de, es, fr, pt).
`stops`	array of object	optional, default []	Sightseeing stops from the search's availableStops the customer wants to add, in any order.
`stops[].locationId`	string	required	locationId of an availableStops entry from search_trips.
`stops[].durationMinutes`	integer	optional	Time at the stop; defaults to the stop's defaultDurationMinutes.
`customStops`	array of object	optional, default []	Stops at places not in availableStops. The trip is then routed and priced through them, so the price will differ from the search.
`customStops[].place`	string	required	Free-text place, like origin/destination.
`customStops[].durationMinutes`	integer	required	Time at the stop.

Returns

status	Meaning
`handover`	`handoverUrl`, a daytrip.com checkout page prefilled with the trip, vehicle and stops, where the traveler enters their name, email and phone and pays. The quoted price is held until `expiresAt`; the link keeps working afterwards but may be re-quoted.
`price_changed`	The price moved since the search. The new price and a fresh `offerId` are returned; call again with it once the traveler accepts.
`offer_expired`	The search option is gone; search again.
`route_not_available`	The trip can no longer be booked.
`invalid_input`	The vehicle type or a stop does not belong to that offer; `message` says what to fix.

Data and privacy

The tools take no personal data and no payment details: a search is a place, a date and a party size, a quote is a vehicle choice and stops. There is no field for a name, email, phone or card, and the connector never asks for one.
Nothing is reserved or charged by any tool. The booking link opens checkout on daytrip.com, where the traveler enters their details and pays. Only then does a booking exist.
The server keeps standard request logs (the calling client's address and name, the tool called, the outcome and timing) for operating the service and preventing abuse. Search inputs are processed to produce the result and are not used to build a profile of the traveler.
The booking link carries the trip selection and a Daytrip attribution; opening it on daytrip.com is subject to the privacy policy and the terms and conditions.

Limits and errors

Rate limit: 60 requests per minute per client IP address, across every MCP method (initialize, tools/list, tools/call, …). Each JSON-RPC message counts as one request; batches are not accepted.
When it is exceeded the server answers HTTP 429 with a Retry-After header, in seconds, and this body. Wait for that long before sending anything else; do not retry in a loop.

{ "statusCode": 429, "message": "ThrottlerException: Too Many Requests" }

Protocol errors are JSON-RPC 2.0 error objects (error.code, error.message): an unknown tool or arguments that fail validation (-32602), a JSON-RPC batch (-32600, HTTP 400), a method other than POST (-32000, HTTP 405), or a credential that does not validate (-32001, HTTP 401). Requests without a credential are never refused for authentication.

{ "jsonrpc": "2.0", "id": 1, "error": { "code": -32602, "message": "Invalid arguments for tool search_trips: …" } }

Tool outcomes such as an unknown place, an unavailable route or an expired offer are not errors: they come back as a normal result with a status and code (listed per tool above). An unexpected failure on the server comes back as a tool result with isError: true and a text explanation; a repeated search_trips or get_quote is safe, a repeated get_booking_link creates another booking draft.

Support

Questions about the connector, a traveler's booking or data: daytrip@daytrip.com, or the Support chat on daytrip.com.

Server card: https://mcp.daytrip.com/mcp/server-card
API catalog: https://daytrip.com/.well-known/api-catalog
Guidance for AI systems: https://daytrip.com/llms.txt
Terms and conditions: https://daytrip.com/en/terms
Privacy policy: https://daytrip.com/en/privacy-policy

What Daytrip is

Connect

Add it to Claude

Example prompts

Tools

search_trips Read-only

Inputs

Returns

get_quote Read-only

Inputs

Returns

get_booking_link Write: creates a booking draft, never a booking or a charge

Inputs

Returns

Data and privacy

Limits and errors

Support

`search_trips` Read-only

`get_quote` Read-only

`get_booking_link` Write: creates a booking draft, never a booking or a charge