MAQAMI Travel
Related Servers
Alternatives to MAQAMI Travel
AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, compare, and book hotels with real-time pricing and availability, supporting multiple location types, star ratings, and price filters.12MIT
Related Servers

Dida Hotel MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to search and book hotels globally with real-time pricing and inventory from over 2 million properties.46MIT
RollingGo Hotel MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, compare, and book hotels worldwide through natural language, with real-time pricing and availability, plus price monitoring and order management.55MIT- AlicenseAqualityDmaintenanceEnables AI agents to search, browse, and book hotels from a database of 2 million properties worldwide. Provides comprehensive hotel search capabilities with location lookup, filtering by amenities, detailed property information, and integrated booking functionality.619 npm1ISC
- AlicenseNot gradedqualityCmaintenanceEnables agents to search, compare, and book hotels across roughly 3 million properties in 200+ countries, paying per booking in USDC on Base via the x402 payment handshake (with a CoinGate fallback) and then polling for order confirmation.MIT
- FlicenseAqualityCmaintenanceHotel booking MCP server — the first transaction-complete hotel booking integration for AI agents. Search 300K+ properties in 140+ countries, get live rates and room details, and generate secure checkout URLs. No payment in the AI conversation — guests complete booking at a hosted checkout page and receive a real hotel confirmation number. Set your own booking fee via Stripe Connect.820 npm3-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search live hotel availability and rates, compare preferred-partner perks with public rates, create a secure one-time payment page, and manage hotel bookings through a licensed travel agency.2-
TDQS
Scored across 41 tools
Many tools have overlapping purposes, especially the hotel-discovery cluster (get_data_hotels, get_data_hotel, get_data_hotel_search, get_data_hotels_semantic_search, get_data_hotels_room_search) and the airport/airline reference tools. Notably get_data_iatacodes and get_data_flights_airports_iatas both return airport code lists, and the three airplane/airline variants are easy to confuse. Descriptions help somewhat but boundaries remain blurry in the get_data_ namespace.
Naming mixes at least three conventions: REST-path style snake_case (get_data_flights_airlines_iatas_iatacode, post_bookings_bookingid_alternative_prebooks), camelCase method names (getExperienceBooking, listBookings, cancelExperienceBooking, getHotelTaxSchema), and verb_noun snake_case (cancel_hotel_booking). The http-mirrored names are also verbose and hard to predict, making the set inconsistent.
41 tools is heavy, but the server spans a genuinely broad multi-vertical domain (hotels, flights, experiences, plus global reference data), which partly justifies the surface. Still, several reference endpoints (three airport tools, three airline tools, duplicate IATA lists) could be consolidated, pushing it above an ideal scope.
Coverage is strong: hotels have search/detail/rates/prebook/get/list/cancel/amend, flights have rates/verify/get/cancel-preview/cancel/services, and experiences have get/cancel-preview/cancel, with comprehensive reference data. Booking creation is intentionally delegated to external checkoutUrls across verticals, so the remaining gap (no in-server booking creation, thin experience surface) is minor and workable.