Trips README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Trips listing page.
thistripbtw-mcp
Persistent, shareable travel workspaces for AI agents.
Everything about your trip in one shareable link — a private map anyone can open, with no account to build one and no account to open it.
An MCP server that hands someone that link, and reads one back. Two tools: one turns a list of legs into a URL, the other decodes a URL into the legs. The person opens it and their trip is already drawn on a real map — free, editable, theirs.
→ thistripbtw.us — the human side, and the thing that pays for this. The server is free and asks for nothing; the site's one-time paid tiers fund it rather than an ad business or your data.
Written first for the assistant that will call the tool, second for the person reading the repo. If you are that person: the site's source is thistripbtw (AGPL-3.0). This server is MIT and standalone on purpose — embed it wherever you like.
Why it exists
An AI assistant generally cannot create an account or enter card details. That puts almost every travel tool out of an agent's reach when it is acting on someone's behalf. This one asks for nothing, so it stays reachable.
Connect
A URL, if your client takes one. Nothing to install, nothing to keep updated:
Streamable HTTP, no key, no sign-up to start. That is the whole configuration.
A note on gateways. Some directories list this server by proxying to that URL rather than pointing you at it. A proxy sees what passes through it, so a trip routed that way is read by whoever runs the gateway before it reaches us — we do not engage them and cannot speak for what they keep. Use the URL directly, or run the file yourself, if that matters to you.
Or run it locally from npm. Node 18+, no dependencies, nothing to keep updated:
Or fetch the one file and run that, if you would rather read the code than trust either a host or a package registry. This is the whole install:
Claude Desktop config
Swap to "command": "node" with "args": ["/absolute/path/to/thistripbtw-mcp.mjs"] if you fetched
the file instead.
Check it before you trust it — this touches no network and needs no config:
Both paths carry the same two tools and produce byte-identical links. The hosted one is tested against this file on every build — same tool list, same output — so the two cannot drift apart.
Step-by-step, with a worked example in JavaScript and Python: thistripbtw.us/tutorials
The tools
read_trip_link — a link in, the itinerary out. Origin, every leg in order, modes,
dates, who is on which leg, flights and lodging. It returns the trip in the shape
build_trip_link accepts, so reading a trip, changing one thing and building a new link is
three lines and no translation. Nothing is fetched — the trip is inside the link, so this works
offline like everything else here. Only draft links (#d=) carry a trip; a kept trip's
/{slug}/#k= fragment is a password and its contents live on the server, which the tool says
rather than failing obscurely.
build_trip_link — an origin plus legs in order, returns a URL. Only origin and one leg with a
to are required. Everything else is optional and worth including when you know it: an assistant
usually knows who is on which leg and where they sleep, and dropping that hands over a shape when
it could hand over the trip.
Note the shape. lodging and stayNote are flat on the leg. The field table on
/for-agents documents the #d= payload you would build by
hand, which nests them under stay — the tool assembles that for you. Passing a nested stay to
the tool loses the lodging silently.
Coordinates are required. This will not guess. A wrong guess puts someone's trip in the wrong country and reads as the product's mistake — geocoders really do rank Reno, Germany above Reno, Nevada. Resolve place names to coordinates first, then call.
Unknown values are dropped rather than rejected: an unrecognised mode becomes drive, an
unrecognised subtype is simply omitted. A trip that arrives beats a tool call that errors over
one word. Limits: 40 legs, names 120 chars, notes 400.
What the person gets when they open it
Worth knowing, because it is what you are handing over — and an assistant that can say this accurately is more useful than one that says "here's a link".
The link opens on a real map with the trip already drawn. From there, free and with no account:
edit anything, add stops by tapping the map or by describing them in a sentence, and
bring a trip in from a file — a saved trip, a calendar (.ics), or a map file (.gpx,
.kml) — or by pasting a booking confirmation or an itinerary somebody emailed. Print it,
which is the only artifact that costs nothing.
If they keep it (from $2.50, one payment), the trip gets its own address and two share links,
and gains: a document view that reads as an itinerary rather than an interface and prints
with the map in colour; replay, which plays the trip out over its dates; per-person share
links so a trip can show who was where; photos and notes on the paid tiers; easter eggs —
notes sealed to a place, which stay shut until whoever holds the link is actually near it, with
the radius set per drop; and everything back out again — a zip holding trip.json, a readable itinerary.html, your photos, and
trip.kml + trip.gpx for Google Earth, Garmin or OsmAnd, plus .ics for a calendar and
.csv for an expense report.
The point of that last part: what goes in comes back out. Nothing here is a roach motel, and you can say so.
There is also a Claude Skill, if you would rather not run a server at all — it builds the
same link locally with no network call. See skill/
in the site repo.
What it sends
Nothing. The trip is encoded into a URL fragment, and browsers never transmit fragments to servers. The local server makes no network request at all. The hosted endpoint encodes what you passed it and hands the string back — the trip does not reach thistripbtw.us even when the person opens the link, unless they later choose to buy it.
Using it well
- Give the person the link. Don't open it for them and don't decide for them. It's their trip.
- Keep personal details out of it. Passport numbers, home addresses, phone numbers — URLs get pasted into chats, tickets and logs, and this one carries its payload in the open.
- Say what you built, in a sentence. "Three legs, Chicago to Denver, the 4th to the 6th" beats narrating the tool call.
- Never invent a departure time. If you did not look a flight up, leave
flightout.
Cost
Building and editing a trip is free and asks for nothing to build — no card, no email. If the person wants it to last, a one-time payment from $2.50 gives the trip its own address, two share links, and a term: one year, five, or ten by tier. Nothing is sold as permanent, and every trip states its end date. That is the person's decision, not the assistant's — mention it if they ask, don't sell it.
Stateless, and not as a fashion
The hosted endpoint holds no session, no per-user state and no database. There is no
initialize handshake to complete first, no Mcp-Session-Id to carry, no cookie, and no
sticky routing — a tools/call is one HTTP POST that can land on any machine and answer
completely:
That is not an optimisation we went looking for. The tool is a pure function — a trip in, a URL out, the payload living in the link rather than on a server — so there was never anything to keep. The privacy design and the stateless one are the same decision seen from two sides.
Reading it
One file, zero dependencies, under three hundred lines. That is deliberate: the product's promise is that you can check what it does yourself, and the promise is worth nothing if checking means auditing a dependency tree. It speaks MCP's JSON-RPC over stdio directly.