Skip to content
Trip Logistics Assistant logo

Trip Logistics Assistant

Claude connector that returns rental car, transfer, eSIM, ticket, luggage storage and flight compensation options with partner booking links.

At a glanceswept 2026-10-12

not read yet

Use

For
Travelers who use Claude to book cars, airport transfers, eSIMs, tickets and luggage storage for trips
Price
Price not read
Activity
Activity not read yet
Company
Domain since 2026domain registered
What people do with it
  • rent a car at an airport with live offers
  • book a private airport transfer for your route
  • claim compensation for a delayed or cancelled flight
The companyeach fact with its source · read 2026-10-14
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-14
  • MCP serverapp.triplogistics/trip-logistics-assistantverified in the MCP registry
  • Stateanswers, 6 toolschecked 2026-10-14
  • Address to connectapi.triplogistics.app/mcp

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Agents tools →

Questions this page answers
  • What is Trip Logistics Assistant?

    Claude connector that returns rental car, transfer, eSIM, ticket, luggage storage and flight compensation options with partner booking links. It is listed in the Atlas under Agents.

  • Who is Trip Logistics Assistant for?

    Travelers who use Claude to book cars, airport transfers, eSIMs, tickets and luggage storage for trips

  • Do people use Trip Logistics Assistant?

    Little sign of use.

  • What are alternatives to Trip Logistics Assistant?

    In Agents, by use: Claude, OpenClaw, Littlebird, Chat Free AI, Landbot, Kin.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.