Skip to main content
Glama
274,731 tools. Last updated 2026-07-08 19:05

"A server for planning travel itineraries and trips" matching MCP tools:

  • Return the description and install snippets for a named tool or server. For tools: the description and the server it belongs to. For servers: local (stdio, via npx) install snippets for every published server, plus remote (HTTP) connection snippets when a hosted endpoint exists — for every supported client, or one client via the client parameter. Call cyanheads_search first to find valid names.
    Connector
  • Live hostel and budget accommodation prices from Hostelworld for any city worldwide. USE FOR: - "What are the cheapest hostels in Paris next week?" - "Find dorm beds in Bangkok for 3 nights from July 10" - "Compare hostel prices in Ljubljana vs Belgrade" - Budget travel planning, accommodation cost context, backpacker routing RETURNS: Per-property dorm and private room prices per night, guest ratings, free cancellation flag, and summary stats (floor/avg/top price). CRITICAL INSTRUCTIONS FOR AGENT: - Always pass date as YYYY-MM-DD format. - currency defaults to EUR. - Use summary.floor for "cheapest" queries, summary.average for general cost context. - free_cancellation=true properties are preferable for uncertain itineraries.
    Connector
  • Start a shared GROUP trip-planning session that friends join by share code — the multi-user counterpart to pricetik_trip_plan. Pass destination (plus optional checkIn/checkOut/title). Returns the session, a shareCode, and a shareUrl (pricetik.com/trips/<code>) — give BOTH to the user so companions can join from their own agent (pricetik_group_trip_join) or vote on the web page without one. Choreography: create → search hotels/activities/tickets as usual → pricetik_group_trip_add_option for the strongest candidates → members vote → organizer finalizes. The creator becomes the session organizer. Requires an authenticated API key; pass an Idempotency-Key header to make retries safe. Sessions are coordinate-only — booking stays per-traveler via the booking-url tools; PriceTik never books on anyone's behalf.
    Connector
  • Searches live rental-car offers for a pickup location and rental period, optionally with a different dropoff location, pickup/dropoff times, driver age, currency, and language. Use this when the user wants to compare available rental cars, prices, vendors, categories, or booking links for a specific trip. Do not use it for flights, hotels, public transport, or general travel planning unless the user has car-rental intent. The tool queries external provider APIs in real time, returns price-ranked results grouped by SIPP/category, and may include affiliate booking links. It does not book cars, modify reservations, charge users, or store user data.
    Connector
  • Searches live flight offers between an origin and destination for given travel dates. Supports one-way (omit return_date) and round-trip searches with flexible passenger counts and cabin class. Use this when the user wants to compare available flights, airlines, prices, layovers, or booking links for a specific route. Do not use it for rental cars, hotels, trains, or general travel planning unless the user has flight-search intent. The tool queries external flight aggregator APIs in real time, returns price-ranked results grouped by number of stops, and includes affiliate booking links. Results and booking links are valid for approximately 15 minutes due to real-time airline pricing. It does not book flights, modify reservations, charge users, or store user data.
    Connector
  • Get the user's saved travel context to personalize recommendations. Returns the user's loyalty programs and elite tiers, home airport, preferred airlines and cabin, preferred hotel chains, typical trip patterns (business vs leisure, budgets, frequent destinations), and any preferences they've stated or that have been learned from past conversations. Call this once at the start of a travel or planning session and weigh it across hotel, flight, and car recommendations — it is the single best source of who this traveler is. Requires a Gondola account (API key). Returns: Formatted travel context, or instructions to build one.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • US visa bulletin data and CBP border wait times. 3 MCP tools for immigration and travel planning.

  • Plan trips collaboratively with AI. Create and manage trips, itineraries, activities, accommodations, transport, tasks, notes, and shared access. Organise day-by-day travel plans, all through MCP tools.

  • List the authenticated user's trips — bookings grouped by destination + overlapping date window. Each trip carries the hotel + all activities, total spend, days-until-departure countdown, and per-member manage URLs. Status filter: 'upcoming' | 'past' | 'all' (default). Requires a bearer API key minted from the dashboard; Open-tier requests get 401. SCOPE: reflects PriceTik order-book fills and agent-assisted direct bookings only — trips the user finished by clicking a pricetik.com/go/ checkout handoff are NOT yet tracked here. An empty result is therefore normal for handoff bookings, not an error; the response carries a `note` field explaining where those bookings live (https://pricetik.com/my-account/bookings) — relay it instead of implying the user has no trips.
    Connector
  • GET /places/:placeID — Get place details Fetch full details for one Google Place ID. Useful for verifying a placeID before sending it to `POST /trips` (which only accepts `type: "city"` placeIDs and rejects venues with a 400). Same shape as a single entry from `GET /places/search`.
    Connector
  • Searches live flight offers between an origin and destination for given travel dates. Supports one-way (omit return_date) and round-trip searches with flexible passenger counts and cabin class. Use this when the user wants to compare available flights, airlines, prices, layovers, or booking links for a specific route. Do not use it for rental cars, hotels, trains, or general travel planning unless the user has flight-search intent. The tool queries external flight aggregator APIs in real time, returns price-ranked results grouped by number of stops, and includes affiliate booking links. Results and booking links are valid for approximately 15 minutes due to real-time airline pricing. It does not book flights, modify reservations, charge users, or store user data.
    Connector
  • "Travel time matrix between [N] origins and [M] destinations" / "drive-time grid via Google Maps" / "transit times between addresses" — N×M distance and duration matrix between many points via Google Maps. Modes: driving, walking, bicycling, transit. Use for delivery routing, multi-stop optimization, transit-heavy planning.
    Connector
  • Full-day departure schedule for a stop. Lists every departure by route and direction for the specified date (defaults to today). Useful for planning or when real-time data isn't needed. For live predictions, use onebusaway_get_arrivals instead.
    Connector
  • Get Booking Search Results Searches Booking.com for accommodations by destination keyword and stay dates (`checkInDate` / `checkOutDate`) with guest composition (rooms, adults, children with ages) and rich filtering: property type, star rating, review score, hotel and room facilities, distance from center, reservation policy, bed preference, travel group, online payment, accessibility, plus optional price range and bedroom/bathroom counts. Pagination is page-based with 25 results per page; locale is controlled by `language` and `currency`. Returns each hotel's `hotelId`, title and Booking URL, location info (city, address, coordinates, distance to center / nearest beach), policies (free cancellation, no prepayment, child/pet stays), price (per stay, before discount, discount, currency), rating, review summary and main photo. Use to power travel-planning agents, OTA price/inventory monitoring, hotel competitor analysis, lead-generation in the hospitality vertical, or to feed `hotelId` / URL into the Booking Place endpoint for full property details.
    Connector
  • Recommend a Cannon Studio workflow for a stated creative or developer goal. Public read-only: no auth, no state changes, no charges; use this for planning, not to create generation jobs.
    Connector
  • GET /trips/:tripID — Get a single trip Single-trip read with the full payload. **This is the canonical endpoint for "who should I meet on this trip?"** — the response embeds a complete `discovery` block (ranked top-10 picks with AI summaries, the full pool of locals + visitors, events in town, and date-overlapping trips). If you only want the discovery block without the trip body, use `GET /trips/:tripID/discovery`. **Key discovery fields agents almost always want:** - `discovery.people` — **ranked top-10 DCers to meet** on this trip, each carrying `score` (higher = better match), mini `profile` (userID, userName, displayName, photo, headline), `reason` (`local` / `visiting` / `event-attendee`), `overlapDays`, `detail`. Sourced from a vector-search + business-context ranking, not just date overlap. - `discovery.whyToMeet` — **AI-written "why you should meet them" paragraph** for each of the top-10, keyed by userID, each `{ text, generatedAt }`. The most useful AI signal in the whole trip product — agents should surface this verbatim when introducing a match. - `discovery.fullPool` — every visible DCer travelling or local during the trip window (typically 5–10× larger than `/trips/overlaps`, which only returns date-window matches). Same row shape as `people` but no `score`. - `discovery.overlappingTrips` — other DCers travelling at the same time/place, each with mini profile attached so no second fetch is needed. This is the same data that `/trips/overlaps` returns, embedded here for convenience. - `discovery.events` — events in the destination city during the trip window. - `discovery.generatedAt` — when the discovery cache was last refreshed. **Also included:** `points` — up to 20 venue/idea notes with optional Google Place data, plus a linked `roomID` for the auto-created trip coordination room. Hidden + guest profiles are filtered out from all discovery lists. The `discovery` block is `null` for newly-created trips until the background sync task runs (~seconds — call `POST /trips/:tripID/refresh` to force-recompute). Open to any authenticated DCer (you can read other DCers' trips too).
    Connector
  • GET /locator/digest — Get locator digest Returns your weekly locator digest — the same data that powers the Friday locator email. Use this to surface trip/event activity around the people and cities a member already follows. The response is composed of four independent sections; pass `?sections=<csv>` to skip any you don't need. Each section is described in full below. - **`homeCity`** — Activity in the city you have set as your home chapter. Null if you have no home city, or if you don't belong to any chapter yet. - **`favoriteCities`** — Per-city digest for cities you have favorited (besides your home city). Each entry lists upcoming trips/events into that city + new ones added since last week. - **`favoritePeople`** — Recent activity from members you follow: their new trips, upcoming trips, recently purchased tickets, and events they've RSVPd to. - **`myTrips`** — For each of your own upcoming trips, the people you're likely to overlap with (chapter leads, local members, and other DCers visiting the same city in the same window). Pass a comma-separated subset to `?sections=...` to omit sections you don't use — useful for narrow integrations and faster responses.
    Connector
  • Get Lenny Zeltser's fill-in-the-blank template for planning a security product strategy. Includes strategic questions organized by section with evidence columns. This server never requests your product plans and instructs your AI to keep them local—guidelines flow to your AI for local analysis. The template is Copyright (c) 2026 Lenny Zeltser; any content you create using it is entirely yours.
    Connector
  • Find the planning portal URL for a UK postcode. Returns the council name, planning system type, and a direct URL to open in a browser. Does NOT return planning application data — scraping is blocked by council portals. Use the returned search_urls.direct_search link to browse applications manually.
    Connector
  • Get your saved boat profile(s). Omit name for the default boat, or use name="*" to list all boats. Tip: use boat speed/consumption with nausika_sea_route and nausika_calculator for trip planning.
    Connector
  • Full-day schedule for a route — all trips, stop sequences, and departure times for the specified date (defaults to today). Returns up to all trips for the route. For live predictions, use onebusaway_get_arrivals at specific stops instead.
    Connector
  • List CamperMate editorial guides and blog posts (route guides, seasonal tips, freedom-camping how-tos, etc.). Returns title, excerpt, image, and a tracked link to the full article on campermate.com. Use this when a user asks for trip inspiration, travel advice, or "what should I read about X". Pass `query` to keyword-filter by title/content/excerpt; omit it for the latest guides.
    Connector