My Next Adventure
Server Details
Create trips, compare variants side by side, and add accommodation, transport and event options.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- MantaCodeDevs/mcp-mynextadventure
- GitHub Stars
- 0
- Server Listing
- MyNextAdventure MCP Server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 25 tools
Tools are mostly cleanly separated by resource and action, and descriptions explicitly cross-reference each other (transport vs getting-around, delete_trip_item vs toggle_event vs select_destination_option). The main wrinkle is granularity: three separate add_* option tools collapse into a single update_destination_option, so an agent must map add-verbs to a shared edit tool, and delete_trip_item is a generic catch-all for four entity types.
Nearly everything follows a predictable verb_noun snake_case pattern (add_*, update_*, select_*, delete_*, list_*, create_*, get_*), with reorder_/duplicate_/toggle_ used sensibly. Only connector_info and whoami break the convention, and they are peripheral utility calls rather than core domain tools.
At 25 tools this is on the heavy side, but the domain genuinely has four entities (trip, variant, destination, option/event) each needing create/read/update/delete plus lifecycle and ordering operations. The count is justified by breadth rather than redundancy, though it sits at the upper bound of comfortable scoping.
CRUD and lifecycle coverage for trips, variants, destinations, options and events is thorough, including duplication, reordering and selection state. Gaps remain at the edges: goals can be listed and added but not edited or removed, a share link can be created but not revoked, trips can only be deleted in the app, and there is no collaborator/member management despite trips being described as shared.
Publisher details
- Operator
- MantaCode sp. z o.o.
- Operator website
- https://mantacode.com/
- Vendor relationship
- First-party
- Documentation
- https://mynextadventure.cloud/mcp/
- Privacy policy
- Not provided
- Trust center
- Not applicable
- Restrictions
- Unknown
Available Tools
25 toolsadd_accommodation_optionAdd Accommodation OptionAInspect
Propose somewhere to stay at a destination — hotel, hostel, apartment, house or camping. Add several options to the same destination so the user can compare them, then use select_destination_option once they pick one. Always include the total cost and currency, otherwise the trip budget will be wrong. Keep name a clean display name — price, town, dates and commentary belong in their own fields, not in name. Use stayDetails only for facts that help choose between this trip's options: never for what is equally true of all of them, and never for a guess.
Inputs: data (required), tripId (required), variantId (required), destinationKey (required).
add_destinationAdd DestinationAInspect
Add a place the traveller will stay at within a variant, in itinerary order (e.g. "Lisbon, Portugal"). Destinations are what accommodation, transport and getting-around options attach to, so add these before adding options. Set isReturnToHome for the final leg home.
Inputs: data (required), tripId (required), variantId (required).
add_eventAdd EventAInspect
Add something to do during the trip — a museum, concert, restaurant, tour or activity. Events belong to the variant rather than to a single destination, and can be scheduled with start/end times or left unscheduled as ideas.
Inputs: data (required), tripId (required), variantId (required).
add_getting_around_optionAdd Getting-Around OptionAInspect
Propose how the traveller moves around locally once at a destination — walking, public transport, rental car, bike, ride share. Use this for local mobility budgets; the journey between destinations belongs in add_transport_option.
Inputs: data (required), tripId (required), variantId (required), destinationKey (required).
add_goalAdd GoalAInspect
Add a travel goal to the user's bucket list from a plain name or a URL — the server works out which and enriches it. Use when the user mentions something they would love to do some day but is not planning right now.
Inputs: data (required).
add_transport_optionAdd Transport OptionAInspect
Propose a way of travelling TO a destination — flight, train, bus, ferry, car. One option per candidate itinerary; add several so the user can compare price against travel time. Set roundTrip when the price covers the return leg too. For moving around once there, use add_getting_around_option instead.
Inputs: data (required), tripId (required), variantId (required), destinationKey (required).
connector_infoConnector InfoARead-onlyIdempotentInspect
Report which build of this connector you are talking to, and whether its tool schemas match the live API. Call this when a tool rejects a field you expect to exist, or accepts one that turns out to have no effect — clients cache tool schemas at connect time, so a connector can advertise an older contract than the API actually has. Takes no arguments and changes nothing.
Inputs: no named parameters.
create_tripCreate TripAInspect
Create a new, empty trip — the container everything else hangs off. This is step 1 of planning: create the trip, then create_variant for the dates, then add_destination, then the accommodation / transport / event options. Ask the user for a name if they have not given one. The free plan allows one active trip of the user's own at a time (status planning or ready; the example trip and trips they were only invited to do not count), so do not create throwaway test trips: check list_trips first and reuse an active one. If this returns 403 because the limit is reached, do not retry. Tell the user they can free the slot by finishing or cancelling their current trip (update_trip with status finished or cancelled; a trip can also be deleted in the app), or upgrade to Premium for unlimited trips, and ask which they want.
Inputs: data (required).
create_variantCreate VariantAInspect
Add an alternative version of the trip — "Beach option" vs "Mountain option", or the same route on different dates. A trip needs at least one variant before it can hold destinations or options, so create one right after create_trip. Dates live on the variant: either exact start/end dates or a flexible window with min/max nights.
Inputs: data (required), tripId (required).
delete_trip_itemDelete Trip ItemADestructiveIdempotentInspect
Permanently delete part of a trip: a variant, a destination, a destination option, or an event. Use only when the user rejects something outright — if they might still want it later, deselect the option or toggle the event instead. Deleting a variant or a destination also deletes everything inside it, so confirm with the user first.
Inputs: target (required), tripId (required), variantId (required), kind, +4 more.
duplicate_variantDuplicate VariantAInspect
Copy a variant, with all of its destinations and options, into a new variant on the same trip. Use when the user wants to explore a tweak ("same trip but a week later", "same route, cheaper hotels") without losing the original.
Inputs: tripId (required), variantId (required).
get_tripGet TripARead-onlyIdempotentInspect
Fetch one trip in full: its variants, destinations, accommodation / transport / getting-around options and events. Call this before changing anything — every other tool needs the variant ids, destination keys and option keys this returns.
Inputs: tripId (required), includeAllOptions.
list_goalsList GoalsARead-onlyIdempotentInspect
List the user's travel goals — the places and experiences on their bucket list ("See the Northern Lights"). Use this for inspiration when starting a new trip, or when the user asks what is on their list. Statuses: 'dreaming' is not planned yet, 'planning' is already linked to a trip, 'visited' is done.
Inputs: status, tripId, collection.
list_tripsList TripsARead-onlyIdempotentInspect
List the trips the user owns or collaborates on. Start here whenever the user refers to a trip by name ("my Japan trip") so you can resolve it to a trip id. Statuses: 'planning' is actively being worked on, 'ready' is planned but not taken yet, 'finished' is in the past, 'cancelled' was dropped. Call with no filters to see everything.
Inputs: status, includeExample.
reorder_destinationsReorder DestinationsAIdempotentInspect
Rearrange the itinerary order of a variant's destinations. Use after adding stops out of order, instead of deleting and re-adding them.
Inputs: data (required), tripId (required), variantId (required).
select_destination_optionSelect Destination OptionAIdempotentInspect
Mark one accommodation / transport / getting-around option as the one the traveller will actually use, or clear the current choice. Always say which kind of option it is; pass optionId to select that option, or omit optionId to deselect whatever is currently selected of that kind. Returns the destination as it now stands, so you can see which option ended up selected. Prefer this over deleting the alternatives — they stay available for comparison.
Inputs: kind (required), tripId (required), variantId (required), destinationKey (required), +2 more.
select_variantSelect VariantAIdempotentInspect
Mark one variant as the trip's chosen plan. Use when the user decides between alternatives; the choice is reversible, so selecting a different variant later is fine.
Inputs: tripId (required), variantId (required).
toggle_eventToggle EventAInspect
Flip an event between "we are doing this" and "just an idea" on the variant. Use when the user commits to, or backs out of, an activity — this keeps the event around, unlike delete_trip_item.
Inputs: tripId (required), eventKey (required), variantId (required).
update_destinationUpdate DestinationAIdempotentInspect
Change a destination's place name, its arrival/departure dates, or its notes. Use this to pin down when the traveller is in each place once the dates firm up, rather than deleting and re-adding the stop.
Inputs: tripId (required), variantId (required), destinationKey (required), data.
update_destination_optionUpdate Destination OptionAIdempotentInspect
Edit an existing accommodation, transport or getting-around option — correct a price, add a booking link, adjust check-in dates. Say which kind of option it is and pass the option key from get_trip. Only the fields you send are changed. On accommodation, use stayDetails only for facts that help choose between this trip's options: never for what is equally true of all of them, and never for a guess.
Inputs: kind (required), tripId (required), optionKey (required), variantId (required), +2 more.
update_eventUpdate EventAIdempotentInspect
Edit an existing event: fix its time, price, location, booking link or notes. Use when the user has new information about an activity that is already on the plan ("the tour starts at 10, not 9").
Inputs: tripId (required), eventKey (required), variantId (required), data.
update_tripUpdate TripAIdempotentInspect
Change top-level trip fields: rename it, set a cover photo, set the owner's budget, or move it through its lifecycle (planning -> ready once the plan is settled, finished or cancelled afterwards). Does not touch variants, destinations or options. Setting status to finished or cancelled frees the free plan's one active trip, so the user can start another; moving a finished or cancelled trip back to planning or ready is refused with 403 on the free plan while another trip is active.
Inputs: tripId (required), data.
update_variantUpdate VariantAIdempotentInspect
Rename a variant, change its dates (exact dates or a flexible window), edit its notes, or set who is travelling. Returns the variant as it now stands — read the response to confirm your change landed rather than assuming it did.
Inputs: tripId (required), variantId (required), data.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Plan trips on a map: routed transport, day-by-day itineraries, and a plan you can share.
Plan trips and find hotels, tours and flights; build day-by-day itineraries. Account required.
Plan trips, search flights and hotels, and keep every booking in one shared itinerary.
Plan group trips with friends: create trips, vote on options, build the itinerary, split costs.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to plan trips by searching flights, accommodations, and activities, and managing itineraries collaboratively with role-based permissions.205 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables conversational planning and editing of trip itineraries, including places, notes, lodging, transit, checklists, expenses, guides, and shareable links.302 npmMIT
- FlicenseNot gradedqualityDmaintenanceConverts natural language travel requests into customizable multi-city itineraries, with tools for planning, editing, and exporting trips across 69 global destinations.-
- AlicenseNot gradedqualityAmaintenanceLets Claude or any MCP-compatible agent view and build trip itineraries through conversation, adding places, notes, hotels, transit legs, car rentals, checklists, and budget expenses, plus searching destinations, hotels, and user-written travel guides. It can also restructure existing trips by renaming days, moving blocks, editing or removing entries, changing dates, and producing shareable links.302 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.