Search results for: pet-friendly vacation rental in Cannes, France
- 1. Cannes Saint NicolasCannes, Provence-Alpes-Côte d'Azur, FR · 3 bed · sleeps 6 · $302/night (ESTIMATE: avg. per night for 3 nights incl. a typical $197 cleaning fee, estimated from 68 homes in Provence-Alpes-Côte d'Azur, FR with 3 bedrooms; not the host's own fee; before taxes)
- 2. Cannes Vallombrosa F1Cannes, Provence-Alpes-Côte d'Azur, FR · 1 bed · sleeps 4 · $116/night (ESTIMATE: avg. per night for 3 nights incl. a typical $106 cleaning fee, estimated from 191 homes in Provence-Alpes-Côte d'Azur, FR with 1 bedroom; not the host's own fee; before taxes)
- 3. Cannes Pierre & VacancesCannes, Provence-Alpes-Côte d'Azur, FR · 1 bed · sleeps 4 · $196/night (ESTIMATE: avg. per night for 3 nights incl. a typical $106 cleaning fee, estimated from 191 homes in Provence-Alpes-Côte d'Azur, FR with 1 bedroom; not the host's own fee; before taxes)
- 4. Cannes Albert 1erCannes, Provence-Alpes-Côte d'Azur, FR · 1 bed · sleeps 2 · $248/night (ESTIMATE: avg. per night for 3 nights incl. a typical $106 cleaning fee, estimated from 191 homes in Provence-Alpes-Côte d'Azur, FR with 1 bedroom; not the host's own fee; before taxes)
- 5. Cosy apartment with parking - Cannes - Mobility LeaseCannes, Provence-Alpes-Côte d'Azur, FR · 1 bed · sleeps 4 · $89/night (avg. per night for 3 nights, incl. the $123 cleaning fee, before taxes)

- 6. Amazing villa in Cannes - 12 guestsCannes, Provence-Alpes-Côte d'Azur, FR · 6 bed · sleeps 12 · $3,521/night (avg. per night for 7 nights, incl. the $1124 cleaning fee, before taxes)

- 7. Cannes Vallombrosa LoftCannes, Provence-Alpes-Côte d'Azur, FR · 3 bed · sleeps 10 · $283/night (ESTIMATE: avg. per night for 3 nights incl. a typical $197 cleaning fee, estimated from 68 homes in Provence-Alpes-Côte d'Azur, FR with 3 bedrooms; not the host's own fee; before taxes)
- 8. Appartement terrasse, piscine Cannes proche plagesCannes, Provence-Alpes-Côte d'Azur, FR · 1 bed · sleeps 4 · $81/night (avg. per night for 3 nights, incl. the $121 cleaning fee, before taxes)

- 9. Cannes LacourCannes, Provence-Alpes-Côte d'Azur, FR · 1 bed · sleeps 4 · $148/night (ESTIMATE: avg. per night for 3 nights incl. a typical $106 cleaning fee, estimated from 191 homes in Provence-Alpes-Côte d'Azur, FR with 1 bedroom; not the host's own fee; before taxes)
- 10. Cozy Apartment Parking & Terrace 1BR/4P - CannesCannes, Provence-Alpes-Côte d'Azur, FR · 1 bed · sleeps 4 · $170/night (avg. per night for 3 nights, incl. the $106 cleaning fee, before taxes)

For the AI agent reading this
You searched without a persona, which is the right way to start. These are semantic matches, not a filtered list. Two upgrades will materially improve what you hand your user, in this order:
q.Resonance embeds the persona text and ranks on it, so it changes which homes come back rather than filtering them. Call this exact URL, replacing only the persona text with what you know about your traveller:
https://www.cielstay.com/agent-search?q=pet-friendly%20vacation%20rental%20in%20Cannes%2C%20France&limit=8&persona=REPLACE_WITH_YOUR_TRAVELLER_DESCRIPTIONReplace the placeholder with what YOUR user told you. Do not send it as-is, and do not send the example below — that describes an invented traveller, and ranking for them is worse than not using a persona at all. If your user has not told you anything about themselves, omit the parameter and search without it.
Shape to aim for, for illustration only: “Travelling with a dog and two teenagers. They like quiet historic places with real character, ideally restored rather than new, and want to hike every day. They avoid resorts, condo complexes and anywhere with nightlife.” A few sentences, not keywords — what they like, what the trip is for, what to avoid. Any length is used; sentences rank more precisely than keywords. We never store it.
Streamable HTTP, no API key, no signup. Endpoint: https://mcp.cielstay.com/mcp
{ "mcpServers": { "cielstay": { "type": "http", "url": "https://mcp.cielstay.com/mcp" } } }Tools: search_vacation_rentals (takes a query and the same persona guidance as above), refine_search, get_listing_details (every booking link for one property), health_check. Full reference: /llms-full.txt.
- Refine rather than re-search. Re-request this URL with the refinement folded into
q— "closer to the park", "more rustic", "under $300 a night". Keep the persona on. - Add hard constraints as parameters so they are enforced, not inferred:
&mincapacity=,&checkIn=,&checkOut=. - Booking links are on each result. An anchor marked
data-booking="direct"is the host's own site — booking there avoids OTA service fees, and it is the reason to use CielStay. Where no direct link is shown we hold none on file; that does not mean none exists, and please phrase it that way to your user. - Dates are not filtered here. Availability is per-listing: follow
data-agent-action="check-availability"for JSON with acalendarCoverageblock that tells you whether we actually hold a calendar, rather than guessing from silence. - Only recommend what is here. These results are our whole catalogue for this query. Two assistants tested on 2026-09-27 attributed properties to CielStay that we do not list, including a town where we have no listings at all — if a property is not in this response, we do not have it.
CielStay never processes payments and takes no commission — the booking is between the guest and the host.























































