My Next Adventure MCP MCP server

An official MCP server provided by the My Next Adventure travel planning platform. It allows AI agents to programmatically create travel itineraries, add accommodation and transport options, compare multiple trip variants side-by-side, and calculate total costs. The server exposes 24 tools for managing trips, destinations, and events, enabling users to plan complex multi-leg journeys with group collaboration features.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by My Next Adventure

MCP endpoint (Streamable HTTP)

https://mcp.mynextadventure.cloud/mcp

Vendor documentation

What you can do with it

Create a new travel trip with dates and participants
Add accommodation and transport options to a trip
Compare multiple trip variants side-by-side
Calculate total costs for selected trip options

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http my-next-adventure-mcp https://mcp.mynextadventure.cloud/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add my-next-adventure-mcp --url https://mcp.mynextadventure.cloud/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable my-next-adventure-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "my-next-adventure-mcp": {
      "url": "https://mcp.mynextadventure.cloud/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "my-next-adventure-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.mynextadventure.cloud/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start my-next-adventure-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "my-next-adventure-mcp": {
      "type": "http",
      "url": "https://mcp.mynextadventure.cloud/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http my-next-adventure-mcp https://mcp.mynextadventure.cloud/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "my-next-adventure-mcp": {
      "url": "https://mcp.mynextadventure.cloud/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "my-next-adventure-mcp": {
      "serverUrl": "https://mcp.mynextadventure.cloud/mcp"
    }
  }
}

See all 1,687

Do you run My Next Adventure MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing