M
MantaCodeDevs/mcp-mynextadventure
A remote Model Context Protocol server that lets an AI
updated 2026-10-23
View on GitHub ↗Direct link · no redirect page
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"mantacodedevs-mcp-mynextadventure": {
"url": "https://mcp.mynextadventure.cloud/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"mantacodedevs-mcp-mynextadventure": {
"type": "http",
"url": "https://mcp.mynextadventure.cloud/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http mantacodedevs-mcp-mynextadventure https://mcp.mynextadventure.cloud/mcp
Claude Code does not read a config file; add the server with this command.
Config file: macOS
~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json, Linux ~/.config/Claude/claude_desktop_config.json. Key names differ by client: Clients & CLI- Star count
- 0 ★ · MantaCodeDevs/mcp-mynextadventure · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
MantaCodeDevs/mcp-mynextadventure;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# MyNextAdventure MCP server
Excerpted from the repository README (abridged)
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 — what most MCP clients send, and what mcp-remote does, or
X-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. |
| update_event | Edit an activity. |
| toggle_event | Flip an activity between committed and "just an idea". |
| delete_trip_item | Permanently delete a variant, destination, option or event. Deleting a whole variant additionally requires confirm: true. |
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 — what most MCP clients send, and what mcp-remote does, or
X-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. |
| update_event | Edit an activity. |
| toggle_event | Flip an activity between committed and "just an idea". |
| delete_trip_item | Permanently delete a variant, destination, option or event. Deleting a whole variant additionally requires confirm: true. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mantacodedevs-mcp-mynextadventure/)
- Source
- awesome · https://github.com/MantaCodeDevs/mcp-mynextadventure
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.