Autonomad Travel

What Autonomad1/autonomad-travel does

Autonomad1/autonomad-travel MCP server exposes travel search and trip-management functions to MCP-compatible agents. It connects agents to live inventory for hotels, flights, activities, events, car rentals, and selected dining and rideshare workflows. The service is intended for agents that need to plan real trips and hand users a path to complete booking, or manage bookings after they are created.

Hotel search covers more than 2 million properties and can return prices, photos, amenities, availability, and cancellation terms. Flight search covers more than 800 airlines and provides schedules, current pricing, and fare comparisons. Activities use the Viator Partner API, while events are sourced from Ticketmaster and SeatGeek. Car rental search is available in more than 15 US metropolitan areas. Rideshare and dining partnerships are still in progress.

How it works

Autonomad1/autonomad-travel can be launched as a local stdio process and connected to an MCP client. The README also identifies a hosted MCP endpoint at mcp.autonomad.ai/mcp, which is already available through the Autonomad connector for Claude and ChatGPT. Local deployments use the booking, identity, and rewards API endpoints configured in the environment.

The server provides tools for individual searches as well as broader orchestration. manage_trip can plan, monitor, and adapt a multi-leg itinerary, including responses to disruptions. Hotel reservations are created with create_booking, while manage_booking supports check-in, check-out, and cancellation workflows. An agent DID is used for autonomous-agent booking authority and rewards attribution; human travelers using the hosted connector do not need to register one.

Setup and configuration

Run the server once with:

npx -y autonomad-travel

It can also be installed globally with npm and started using the autonomad-travel executable. For a local configuration, the README shows AGENT_DID and BOOKING_API_URL in the MCP client environment. AGENT_DID is required for bookings and can be registered through autonomad.ai. The API URL defaults to https://api.autonomad.ai.

Additional configuration variables are available for identity resolution and reward settlement: IDENTITY_API_URL and REWARD_API_URL. Both default to the same Autonomad API host. The project is licensed under MIT.

Tools and capabilities

Autonomad1/autonomad-travel exposes these MCP tools:

• search_hotels: Find available hotels with commercial and property details.
• search_flights: Compare live flight schedules, fares, and airlines.
• book_transport: Find itinerary-timed car rental and rideshare quotes.
• book_dining: Search restaurants that fit the trip schedule.
• manage_trip: Coordinate, monitor, and adjust complete itineraries.
• create_booking: Reserve hotel rooms with commission and delegation details.
• manage_booking: Handle check-in, check-out, and cancellation actions.
• submit_feedback: Send structured post-stay reviews for travel categories.
• check_rewards: Query $NOMD balances, settlement history, and redemption options.

It also exposes autonomad://hotels for hotel catalog and live availability data, plus autonomad://profile for the agent profile, reputation score, and tier status.

Limitations and notes

Coverage is not uniform across all travel categories. Car rental is limited to the listed US metro coverage, while rideshare and dining integrations are described as in progress. Wellness is marked as coming soon. The README documents testing with Claude Desktop and Cline, along with broader compatibility through MCP-compatible clients.

Rewards depend on completed bookings and use the Autonomad agent identity and settlement system. The $NOMD reward, tier, and redemption features are therefore relevant mainly to autonomous agents with a registered DID, not just read-only search clients.

Getting started with this Autonomad1/autonomad-travel MCP server

Always refer to the official documentation for the most accurate and up-to-date information.