MyNextAdventure MCP Server
Enables resolving place IDs and retrieving place details through Google Places when adding or updating accommodation, transport, activity, and destination options.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MyNextAdventure MCP Server Plan a trip to Paris for 5 days and add a hotel and a museum visit."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MyNextAdventure MCP server
A remote Model Context Protocol server that lets an AI assistant plan trips in MyNextAdventure — create a trip, lay out the itinerary, propose flights and hotels, add things to do, and share the result.
It runs as a stateless Cloudflare Worker and is a thin, authenticated proxy in front of the MyNextAdventure public API: it holds no trip data of its own, and forwards every call to the API under the caller's own API key.
Production:
https://mcp.mynextadventure.cloud/mcp(Streamable HTTP)Upstream API:
https://api.mynextadventure.cloud(v1 public API)
Authentication
Every request needs a MyNextAdventure API key. Create one in the app under Settings → API keys, then send it as either:
Authorization: Bearer <api-key>— what most MCP clients send, and whatmcp-remotedoes, orX-API-Key: <api-key>— for clients that only let you set custom headers.
The worker forwards it to the API as X-API-Key. Requests without a key get a 401.
Whatever the key can do, the assistant can do: keys are per-user, so the assistant only ever
sees that user's trips.
Where your key lives. The server is stateless: your key is read from the headers of each request, used to make that one call to the MyNextAdventure API, and never stored — there is no session storage and no Durable Object holding it between requests. It is never logged and is not shared between requests or users. Revoke a key any time in the app under Settings → API keys.
Related MCP server: wanderlog-mcp
Tools
24 tools, covering the operations conversational planning actually needs. Each one is a curated view over a MyNextAdventure API operation — see Regenerating the tools.
Tool | What it does |
| Which account the API key belongs to (handy for checking the connection). |
| List the user's trips; filter by status ( |
| One trip in full — variants, destinations, options, events. Needed before any edit. |
| Create a new, empty trip. |
| Rename, set a cover photo, or move the trip through its lifecycle. |
| Create/refresh a public read-only share link. |
| Add an alternative plan (dates live here: exact or flexible). |
| Copy a variant with everything in it. |
| Rename a variant, change its dates or notes. |
| Mark a variant as the chosen plan. |
| Add a stop to a variant, in itinerary order. |
| Change a stop's place name, dates or notes. |
| Reorder the stops in a variant. |
| Propose a place to stay at a destination. |
| Propose a way of getting to a destination. |
| Propose local mobility (public transport, rental car, …). |
| Edit an existing option of any of the three kinds. |
| Select — or, with no |
| Add an activity (museum, concert, restaurant, tour) to a variant. |
| Edit an activity. |
| Flip an activity between committed and "just an idea". |
| Permanently delete a variant, destination, option or event. Deleting a whole variant additionally requires |
| List the user's travel goals / bucket list. |
| Add a goal from a name or a URL. |
The server also ships MCP instructions describing the data model
(trip → variants → destinations → options, with events on the variant) and the usual
order of operations, so a client does not have to guess the workflow.
Not exposed yet, though the API supports them: collaborator access management and invites, voting, collections, invite tokens, goal↔trip linking, API key management, and trip deletion.
Tool annotations
Every tool publishes a human-readable title (also as annotations.title; set in
scripts/tool-manifest.ts, required by the Claude connectors directory) and all four MCP
ToolAnnotations
hints on tools/list, so clients can tell at a glance what is safe to run unattended:
Hint | True for |
| The 4 lookups: |
|
|
| The |
| The 8 tools whose request can reach a third-party API: the three read tools (Kinde profiles, Google Places, currency conversion) plus |
The spec's defaults are the pessimistic ones (destructiveHint and openWorldHint both
default to true), so the manifest requires all four to be stated per tool rather than
inherited. test/annotations.test.ts holds the expected classification tool by tool and
cross-checks readOnlyHint against the HTTP verb each tool actually issues.
Connecting
Claude Desktop
Settings → Developer → Edit Config, then add:
{
"mcpServers": {
"mynextadventure": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.mynextadventure.cloud/mcp",
"--header",
"Authorization: Bearer ${MNA_API_KEY}"
],
"env": { "MNA_API_KEY": "your-api-key" }
}
}
}Restart Claude Desktop; the tools appear under the connector.
claude.ai / Claude Code
Add a custom connector pointing at https://mcp.mynextadventure.cloud/mcp and set the
Authorization: Bearer <api-key> header. From Claude Code:
claude mcp add --transport http mynextadventure https://mcp.mynextadventure.cloud/mcp \
--header "Authorization: Bearer <api-key>"ChatGPT
Settings → Connectors → Add custom connector, MCP server URL
https://mcp.mynextadventure.cloud/mcp, authentication "custom header" with
X-API-Key: <api-key> (or Authorization: Bearer <api-key>).
Any other MCP client
Streamable HTTP at /mcp. GET / returns a small JSON health document with the endpoint
and tool count.
Local stdio
The same tools over stdio, for clients that launch a subprocess, with the key in
MNA_API_KEY. Glama's build check runs this behind mcp-proxy.
npm ci
MNA_API_KEY=<api-key> npm run start:stdioDevelopment
npm install
npm run dev # wrangler dev on http://localhost:8787
npm test # vitest: request building, schemas, generator freshness
npm run type-check # tsc --noEmit
npm run generate:tools # regenerate src/generated/tools.ts from the OpenAPI spec
npx tsx scripts/smoke.ts # drive the MCP protocol against localhost:8787scripts/smoke.ts performs a real handshake (initialize → tools/list → one tools/call),
reading the API key from $MNA_API_KEY or ~/.config/mna/credentials. It refuses to call
mutating tools unless --force is passed. To exercise write tools without touching real
data, point the worker at a local mock:
npx wrangler dev --var MNA_API_BASE_URL:http://localhost:8899Regenerating the tools
Tool schemas are generated, not hand-written:
spec/openapi-v1.json (the API's OpenAPI snapshot)
+
scripts/tool-manifest.ts (which operations become tools; names, descriptions, annotations)
↓ scripts/generator.ts
src/generated/tools.ts (committed; zod input schemas, annotations + request builders)To add or change a tool, edit scripts/tool-manifest.ts and run npm run generate:tools.
Never edit src/generated/tools.ts by hand — a test fails if it drifts from the spec.
A manifest entry names one API operation, or groups several body-less operations behind a
discriminator argument (delete_trip_item's target, select_destination_option's
action) to keep the tool count down. Path params can be renamed (id → tripId), query
params can be narrowed to enums, and descriptions can be overridden — everything else,
including the request-body schemas, comes from the spec.
Each entry must also carry annotations (all four MCP hints; see
Tool annotations). TypeScript enforces this, so a new tool cannot be
added without classifying it, and test/annotations.test.ts checks the result against an
expected table.
Deployment
npm run deploy (wrangler) — production only, so it is gated on a maintainer; CI never
deploys this worker.
Development
npm ci
npm run type-check
npm test # includes a drift test: src/generated/tools.ts must match the generator output
npm run dev # wrangler devTools are generated from the vendored OpenAPI snapshot in spec/openapi-v1.json
(canonical live spec: https://api.mynextadventure.cloud/api/v1/openapi.json) via
scripts/generate-tools.ts. Regenerate after refreshing the snapshot.
This repo is the deployable source for mcp.mynextadventure.cloud. Development also
happens in the My Next Adventure monorepo and is synced here on release. Issues and
PRs welcome.
License
MIT
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.
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.
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.
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, or move it through its lifecycle (planning -> ready once the plan is settled, finished or cancelled afterwards). Does not touch variants, destinations or options.
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…
TDQS
Scored across 25 tools
Each tool targets a distinct resource and action, with explicit disambiguation between similar families such as add_transport_option (between destinations) versus add_getting_around_option (local mobility), and toggle_event versus delete_trip_item. Polymorphic tools like update_destination_option and select_destination_option use a kind argument but their descriptions clearly explain the boundaries.
The set overwhelmingly follows a predictable verb_noun snake_case pattern (list_trips, create_variant, add_accommodation_option, update_event). The only deviations are whoami and connector_info, which are informational tools rather than CRUD operations, so the convention is still easy to follow.
Twenty-five tools is on the high side, but the trip-planning domain has several nested resources (trips, variants, destinations, three option kinds, events, goals) that justify most tools. Some option-add tools could potentially be consolidated, but each still earns its place.
Core lifecycle coverage is strong: trips, variants, destinations, options, and events all have create/read/update/select/delete paths. Minor gaps remain, such as no direct delete_trip operation, no revoke for share links, and goals only supporting list/add without update or delete.
Maintenance
Related MCP Connectors
Plan and manage TravelOwl trips from ChatGPT, Claude and other MCP assistants.
Read and update your Everway trips and itineraries from any MCP-compatible AI assistant.
Travel tools for AI agents: plan and edit real trips, search stays and tours, import travel videos.
AI marketplace — flights, tours, activities, transport & more via MCP. No auth required.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible agents to view, create, and edit trip itineraries through conversation, adding places, notes, hotels, transit legs, car rentals, checklists, and budget expenses. Also supports searching places, guides, and hotel deals, plus updating trip dates, day names, and custom sections.302 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible agents to view and build trip itineraries through conversation, including places, notes, hotels, transit, rentals, checklists, expenses, and search across places, hotels, and guides.302 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible agents to view and build trip itineraries through conversation, adding places, notes, hotels, transit, checklists, and expenses while managing dates and custom sections.302 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude or any MCP-compatible agent to view, build, and edit trip itineraries through conversation, including places, notes, hotels, transit, checklists, expenses, and custom sections.302 npmMIT