New: NomadPoint now finds the fastest order for your day's stops. Get the update

NomadPoint

Developers and agents

01

MCP server

The NomadPoint MCP server lets an agent read and edit one user’s trips: journeys, stays, flights, accommodation, activities, expenses and budgets, plus visa and country information. It speaks streamable HTTP and is listed in the MCP registry as app.nomadpoint/nomadpoint.

https://nomadpoint.app/mcp
02

Access tokens

Keys are self-serve and managed in the app. A signed-in Pro user opens Settings > Claude / MCP, taps Connect Claude, and copies a prompt that carries a personal access token (np_mcp_…). Send it as Authorization: Bearer on every request. Regenerate Token replaces it; Disconnect revokes it immediately. Every call is scoped to the token owner’s trips. Step by step: auth.md.

03

WebMCP tool, no account

Every page on nomadpoint.app registers calculate_schengen_days with document.modelContext. Pass trips as a list of { entry, exit } dates in YYYY-MM-DD and an optional asOf; it returns days used, days remaining, the latest date a stay can run to, and the next date a day frees up. It runs in the page and uploads nothing.

04

Agent skill

The nomadpoint skill teaches an agent the trip model and how to use the MCP tools well.

npx skills add eladkishon/nomadpoint-skills
05

Machine-readable files

llms.txt · agents.md · pricing.md · ard.json. Any page is available as markdown: add .md to its URL or send Accept: text/markdown.