Skip to main content
Glama

Related Servers

Alternatives to flights-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Flexible multi-leg, multi-airport flight search that finds the cheapest route across an entire itinerary — available as a CLI and as an MCP server for AI agents.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Flight search for AI agents: flexible-date cheapest round-trips with a good-price verdict from historical data. Hosted remote MCP, free, no key.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to search and retrieve live flight information through the Duffel API, supporting one-way, round-trip, and multi-city itineraries with flexible parameters such as dates, cabin class, passenger counts, and connection limits. It also retrieves detailed offer information, letting AI agents and Claude compare routes and prices conversationally.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables searching Google Flights and getting structured, price-sorted flight options locally through MCP clients like Claude or Codex, with no API key or central server required.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to find the cheapest dates to fly a route via Google Flights, supporting one-way and round-trip searches through multiple backends. It provides a tool that can search date ranges, filter by nonstop, seat, currency, and force a particular backend.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables real-time flight fare searches across date ranges and multiple destinations, with historical price insights and booking links. Provides one-way and round-trip search tools through MCP.
      4
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    search_flights and resolve_airports have entirely distinct purposes: one performs live fare lookups, the other does offline name-to-IATA resolution. There is no overlap in intent, so an agent can select correctly without hesitation.

    Naming Consistency5/5

    Both names follow a clean verb_noun snake_case pattern (search_flights, resolve_airports). The convention is predictable and consistent throughout the two-tool surface.

    Tool Count3/5

    Two tools is thin for a flight-search domain; resolve_airports is really a supporting lookup rather than a peer operation. It is not wrong, but the surface feels minimal and could reasonably include one or two more operations.

    Completeness4/5

    The stated purpose is read-only fare search, and the pair covers lookup plus resolution with no dead ends for that scope. Minor gaps exist (e.g. no explicit round-trip or multi-passenger handling surfaced as separate operations), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues