How do I install My Next Adventure?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does My Next Adventure need an API key?

No required environment variable is listed on this record.

What transport does My Next Adventure use?

My Next Adventure is reached over HTTP.

When was My Next Adventure last checked?

Last checked 2026-11-07. Create trips, compare variants side by side, and add accommodation, transport and event options.

My Next Adventure MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.mynextadventure.cloud/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http cloud.mynextadventure-trip-planner https://mcp.mynextadventure.cloud/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "cloud.mynextadventure-trip-planner": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.mynextadventure.cloud/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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 what mcp-remote does, or
X-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.

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
`whoami`	Which account the API key belongs to (handy for checking the connection).
`list_trips`	List the user's trips; filter by status (`planning`, `ready`, `finished`, `cancelled`).
`get_trip`	One trip in full — variants, destinations, options, events. Needed before any edit.
`create_trip`	Create a new, empty trip.
`update_trip`	Rename, set a cover photo, or move the trip through its lifecycle.
`create_trip_share_link`	Create/refresh a public read-only share link.
`create_variant`	Add an alternative plan (dates live here: exact or flexible).
`duplicate_variant`	Copy a variant with everything in it.
`update_variant`	Rename a variant, change its dates or notes.
`select_variant`	Mark a variant as the chosen plan.
`add_destination`	Add a stop to a variant, in itinerary order.
`update_destination`	Change a stop's place name, dates or notes.
`reorder_destinations`	Reorder the stops in a variant.
`add_accommodation_option`	Propose a place to stay at a destination.
`add_transport_option`	Propose a way of getting to a destination.
`add_getting_around_option`	Propose local mobility (public transport, rental car, …).
`update_destination_option`	Edit an existing option of any of the three kinds.
`select_destination_option`	Select — or, with no `optionId`, deselect — an option.
`add_event`	Add an activity (museum, concert, restaurant, tour) to a variant.

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.

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.

Development

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:8787

scripts/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:8899

Regenerating the tools

Tool schemas are generated, not hand-written:

apps/server/openapi-v1.json   (the API's OpenAPI snapshot, kept fresh by server CI)
        +
scripts/tool-manifest.ts      (which operations become tools, their names and descriptions)
        ↓  scripts/generator.ts
src/generated/tools.ts        (committed; zod input schemas + 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.

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 dev

Tools 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

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install My Next Adventure?

Does My Next Adventure need an API key?

What transport does My Next Adventure use?

When was My Next Adventure last checked?

Documentation

MyNextAdventure MCP server

Authentication

Tools

Connecting

Claude Desktop

claude.ai / Claude Code

ChatGPT

Any other MCP client

Development

Regenerating the tools

Deployment

Development

License