A
licenseNot graded
qualityB
maintenanceEnables read-only research of public Outsite locations, quoted stay rates, and individual room calendars.
MIT
WonderKit Discover
Server Details
Read-only city guides and public itineraries for family and group trips.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Score is being calculated.
Available Tools
7 toolscontinue_in_wonderkitContinue in WonderKitRead-onlyIdempotentInspect
Use this when someone wants to save, share, or keep working on a plan from a public guide or itinerary. Returns the WonderKit web links for that city guide, itinerary, and the guest planner. This server cannot save or share anything itself.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City name or WonderKit city key, such as "Paris" or "paris-france". | |
| slug | No | Optional itinerary slug to link a specific public plan. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| hint | No | |
| note | Yes | Read-only reminder; not user content |
| found | No | false when the lookup did not resolve |
| links | Yes | |
| reason | No | unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, … |
| region | No | The state, country, or area the city ask was read as |
| matches | No | Candidate cities when the name is ambiguous |
| nearest | No | Covered cities in or near the asked-for area. Not the city that was asked for |
| planUrl | No | Guest planner link for the destination as asked; it plans any city |
| guideList | No | |
| suggestions | No | Near-miss spellings, or same-name cities elsewhere, when the name is unknown |
| itinerariesUrl | No | WonderKit itineraries for this city |
| planDescription | No | One line saying what planUrl opens |
find_activitiesFind activitiesRead-onlyIdempotentInspect
Use this when someone asks what to do in one city: weekend ideas, events, food, or kid-friendly, date-night, or group activities. Returns published picks from the WonderKit city guide and the page URL. Returns single activities, not multi-day plans, and cannot see anyone's own trips.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City name or WonderKit city key, such as "Paris" or "paris-france". | |
| query | No | Optional words to match against activity titles and descriptions, such as "museums" or "dinner". Plurals match singulars. | |
| audience | No | Who the plan is for: families, friends, or couples. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| city | No | |
| hint | No | |
| note | Yes | Read-only reminder; not user content |
| found | No | false when the lookup did not resolve |
| reason | No | unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, … |
| region | No | The state, country, or area the city ask was read as |
| cityKey | No | |
| matches | No | Candidate cities when the name is ambiguous |
| nearest | No | Covered cities in or near the asked-for area. Not the city that was asked for |
| pageUrl | No | WonderKit page to cite |
| planUrl | No | Guest planner link for the destination as asked; it plans any city |
| audience | No | |
| truncated | No | |
| activities | No | |
| suggestions | No | Near-miss spellings, or same-name cities elsewhere, when the name is unknown |
| itinerariesUrl | No | WonderKit itineraries for this city |
| planDescription | No | One line saying what planUrl opens |
get_itineraryGet itineraryRead-onlyIdempotentInspect
Use this when someone wants the full plan for one public itinerary, by its slug: day-by-day or themed stops with real venues and map links, rainy-day and where-to-eat sections, and the best season. Returns dayCount and stopCount (anchors plus backups; before 2026-09-28 stopCount held the day count), the page URL, and planUrl, which opens the WonderKit planner prefilled from this plan. Read-only; it cannot change a plan.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City name or WonderKit city key, such as "Paris" or "paris-france". | |
| slug | Yes | Itinerary slug from list_itineraries or search_itineraries, such as "3-day-weekend-for-couples". |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| url | No | WonderKit page to cite |
| city | No | |
| days | No | |
| hint | No | |
| lede | No | One-line promise of the plan |
| note | Yes | Read-only reminder; not user content |
| slug | No | |
| found | No | false when the lookup did not resolve |
| shape | No | |
| title | No | |
| reason | No | unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, … |
| region | No | The state, country, or area the city ask was read as |
| season | No | |
| cityKey | No | |
| matches | No | Candidate cities when the name is ambiguous |
| nearest | No | Covered cities in or near the asked-for area. Not the city that was asked for |
| planUrl | No | Give this to the person to plan this trip: the WonderKit planner prefilled from this itinerary |
| summary | No | |
| audience | No | |
| dayCount | No | |
| imageUrl | No | Hero photo of the plan |
| sections | No | Rainy-day backups, where to eat, and similar |
| stopCount | No | Named stops (anchors plus backups), not days; see dayCount. Until 2026-09-28 this carried the day count |
| truncated | No | |
| markdownUrl | No | The same plan as Markdown |
| suggestions | No | Near-miss spellings, or same-name cities elsewhere, when the name is unknown |
| lastReviewed | No | |
| itinerariesUrl | No | WonderKit itineraries for this city |
| planDescription | No | One line saying what planUrl opens |
list_citiesList citiesRead-onlyIdempotentInspect
Use this when someone asks which cities WonderKit covers or needs a valid city key. Lists cities that have a published city guide of real things to do, with their keys. Reads public guides only; it cannot plan, save, or look up a private trip.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| hint | No | |
| note | Yes | Read-only reminder; not user content |
| found | No | false when the lookup did not resolve |
| cities | No | |
| reason | No | unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, … |
| region | No | The state, country, or area the city ask was read as |
| matches | No | Candidate cities when the name is ambiguous |
| nearest | No | Covered cities in or near the asked-for area. Not the city that was asked for |
| planUrl | No | Guest planner link for the destination as asked; it plans any city |
| truncated | No | |
| suggestions | No | Near-miss spellings, or same-name cities elsewhere, when the name is unknown |
| itinerariesUrl | No | WonderKit itineraries for this city |
| planDescription | No | One line saying what planUrl opens |
list_itinerariesList itinerariesRead-onlyIdempotentInspect
Use this when someone wants to browse WonderKit's public multi-day itineraries and place guides, for all cities or one city and audience. Plans that are in season this month come first. Each summary has dayCount (days or themed sections) and stopCount (anchors plus backups; before 2026-09-28 stopCount held the day count). Browses by city and audience only; it does not rank by a free-text description. Does not book or edit a trip.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City name or WonderKit city key, such as "Paris" or "paris-france". | |
| audience | No | Who the plan is for: families, friends, or couples. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| city | No | |
| hint | No | |
| note | Yes | Read-only reminder; not user content |
| found | No | false when the lookup did not resolve |
| reason | No | unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, … |
| region | No | The state, country, or area the city ask was read as |
| cityKey | No | |
| matches | No | Candidate cities when the name is ambiguous |
| nearest | No | Covered cities in or near the asked-for area. Not the city that was asked for |
| planUrl | No | Guest planner link for the destination as asked; it plans any city |
| truncated | No | |
| itineraries | No | |
| suggestions | No | Near-miss spellings, or same-name cities elsewhere, when the name is unknown |
| itinerariesUrl | No | WonderKit itineraries for this city |
| planDescription | No | One line saying what planUrl opens |
| availableAudiences | No |
plan_trip_linkPlan trip linkRead-onlyIdempotentInspect
Use this when someone wants to start planning their own trip to a destination in WonderKit. Returns one guest-planner link with the city (and vibe) filled in, plus a one-line description. It creates nothing and cannot book; the person adds dates and travelers in the planner. The link is a planner, not a citable guide page.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | Destination as the person said it, such as "Lisbon" or "Asheville, NC". Any city works. | |
| vibe | No | The feel they want, if they said. | |
| endDate | No | Last day, YYYY-MM-DD, if they gave one. | |
| kidsAges | No | Ages of children travelling, if any. | |
| startDate | No | First day, YYYY-MM-DD, if they gave one. | |
| travelers | No | How many people are going. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | Guest planner link to give the person |
| hint | No | |
| description | Yes | One line saying what the link opens |
| notPrefilled | No | Inputs the link cannot carry |
search_itinerariesSearch itinerariesRead-onlyIdempotentInspect
Use this when someone describes the trip they want, such as "romantic weekend in October", "museums with kids", or "Christmas markets", and needs matching public itineraries across cities. Ranks by the words they used, who it is for, and season fit. Pass a city to stay in one city. Do not use it to create or save a trip; it only reads published guides.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City name or WonderKit city key, such as "Paris" or "paris-france". | |
| limit | No | How many results to return, up to 8. | |
| month | No | Travel month, 1-12. Boosts plans whose peak months include it. Wins over season. | |
| query | No | What they want, in their words, such as "romantic weekend", "museums with kids", or "fall foliage". Plurals match singulars. | |
| shape | No | day-plan for a day-by-day plan, places-guide for a themed list of places. | |
| season | No | Season they are travelling in. "now" means the current month. Northern-hemisphere seasons. | |
| audience | No | Who the plan is for: families, friends, or couples. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| city | No | |
| hint | No | |
| note | Yes | Read-only reminder; not user content |
| found | No | false when the lookup did not resolve |
| reason | No | unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, … |
| region | No | The state, country, or area the city ask was read as |
| cityKey | No | |
| matches | No | Candidate cities when the name is ambiguous |
| nearest | No | Covered cities in or near the asked-for area. Not the city that was asked for |
| planUrl | No | Guest planner link for the destination as asked; it plans any city |
| rankedFor | No | The month or season used for the season-fit ranking |
| truncated | No | |
| itineraries | No | Best match first |
| suggestions | No | Near-miss spellings, or same-name cities elsewhere, when the name is unknown |
| itinerariesUrl | No | WonderKit itineraries for this city |
| planDescription | No | One line saying what planUrl opens |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
7 tool updates
- First observed
continue_in_wonderkit - First observed
find_activities - First observed
get_itinerary - First observed
list_cities - First observed
list_itineraries - First observed
plan_trip_link - First observed
search_itineraries
Related MCP Connectors
Read-only European city sights: search, nearby, walking routes and itineraries in 6 languages.
Open places, menus, ratings and booking routes in 119 travel destinations. Read-only, no key needed.
91Read-only public itinerary previews, observed round-trip fares, and flight savings verified today.
Free city-walk planner: day-by-day self-guided walking itineraries for 50+ cities. No sign-up.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to access 21 read-only tools for local travel planning, including trip and itinerary validation, budget calculation, booking requirements, integration provider status, flight/train/accommodation/activity searches, route/weather/currency lookups, and travel source search.MIT
- FlicenseNot gradedqualityDmaintenanceConverts natural language travel requests into customizable multi-city itineraries, with tools for planning, editing, and exporting trips across 69 global destinations.-
- AlicenseBqualityBmaintenanceProvides AI agents with a structured API for travel planning, enabling them to read trip data, search places, calculate routes, and create/validate itinerary change proposals that require explicit human approval before being applied.15MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.