MCP server

My Next Adventure runs its own remote MCP server, so your AI assistant can plan a trip with you and leave something structured behind: a trip with variants, options and costs that outlives the chat window. It exposes 24 tools and covers the planning surface end to end — including creating the trip, not only filling in one you already made.

Endpoints

`https://mcp.mynextadventure.cloud/mcp`	Streamable HTTP. Use this one if your client supports it.
`https://mcp.mynextadventure.cloud/sse`	Server-sent events, for clients that still expect the SSE transport.

Authenticate with an API key from your account, sent as Authorization: Bearer <API key> or X-API-Key: <API key>. /health reports the server status and tool count without a key.

What the 24 tools cover

Trips (5)	list your trips, read one in full, create, update, and generate a public share link
Variants (4)	create a variant, duplicate an existing one, update it, mark it as the selected one
Destinations (3)	add a destination to a variant, update its dates and notes, reorder the legs
Options (5)	add accommodation, transport and getting-around options, update them, select the winner
Events (3)	add an event, update it, toggle whether it counts towards the total
Travel goals (2)	list your travel goals and add a new one
Account & cleanup (2)	confirm which account the key belongs to, delete an item you no longer want

Not over MCP yet: extraction from a pasted link or screenshot, voting, and managing collaborators. Those live in the web app, and voting and collaborators are also in the CLI.

Get your API key

Open the menu under your profile picture, top right.
Select API keys.
Generate one and copy it. It is shown only once, because we store only a hash of it.

Connect your client

Claude Desktop, Claude Code, Cursor, Windsurf, Cline

These read a JSON config file. Add the server through the local mcp-remote bridge, which passes your API key as a header:

{
  "mcpServers": {
    "my-next-adventure": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mynextadventure.cloud/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

claude.ai integrations and ChatGPT connectors

Anything that adds a remote MCP server by URL can talk to us directly, with no local bridge. Add the streamable HTTP endpoint as a custom connector or integration and give it your API key where it asks for a token or a custom header:

URL:    https://mcp.mynextadventure.cloud/mcp
Header: Authorization: Bearer YOUR_API_KEY

If a client insists on an OAuth-authenticated server and leaves you nowhere to put a key, use the mcp-remote configuration above instead.

Then just ask

Once it is connected, using it looks like this:

"Create a trip called Lisbon in May, two adults and two kids."
"Make a second variant of the Lisbon trip where we drive instead of flying."
"Add these three hotels as accommodation options and select the cheapest one."
"What do my two Lisbon variants cost, and where does the difference come from?"
"Give me a share link for the Lisbon trip so I can send it to the others."

Prefer a terminal?

The same API has an open-source CLI, mna, with 61 commands — including the parts MCP does not cover yet, such as inviting collaborators and voting. It also ships as a Claude Code skill.

npm install -g @mantacodedevs/mna-cli
# or: brew install mantacodedevs/tap/mna

mna login
mna trips list

github.com/MantaCodeDevs/mna-cli

Demo

This was recorded against an earlier build of the server, which had fewer tools. The setup flow is unchanged.

API, CLI and MCP access are included in the free tier.