Aviasales Flight Prices
Flight price search via Aviasales/Travelpayouts: fares by route, cheapest days, flexible dates.
Connector by stufently · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/stufently-aviasales-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 13 read · 0 write · 0 deleteRead-only
- Secrets
- 1 (API keys, tokens or passwords)
- Install scripts
- None found
- Runs as
- Python package
Tools by what they do 13
Read from the source code; the running server may list different tools.
Read 13 · Look things up without changing anything.
find_nearest_airportsget_alternative_directionsget_city_directionsget_flexible_date_pricesget_latest_pricesget_popular_directionsget_prices_calendarlookup_airlineslookup_airportslookup_citieslookup_countriessearch_by_price_range
Show 1 more tools
search_flights
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
AVIASALES_API_TOKEN
Other settings (environment variables or headers).
AVIASALES_DEFAULT_CURRENCYAVIASALES_MARKETAVIASALES_PARTNER_ID
Network hosts it talks to 5
api.travelpayouts.com· found in codegithub.com· found in codeglama.ai· found in codesupport.travelpayouts.com· found in codetravelpayouts.com· found in code
Files it touches
- Any path the agent passes to its tools
Tools (13)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
find_nearest_airportsread-onlyFind the airports closest to a place name or to a latitude and longitude. Use when the user asks which airport to fly into for a town, a resort, or a point on the map. `lookup_airports` only matches a name, and the nearest airport is rarely named after the town, so call this tool for that question. Feed the returned city code, not the airport code, to `search_flights` for fares. Pass either `near` (resolved against the city and airport datasets) or an explicit `latitude`/`longitude` pair. Args: near: Place name or IATA code to search around (e.g. "Pattaya", "UTP"). latitude: Latitud…
get_alternative_directionsread-onlyGet prices for nearby airports and cities around a chosen route. Use when the traveller can fly from or into a different airport and wants those fares. To learn which airports are near a place, use `find_nearest_airports` first; for the named city pair only, use `search_flights`. Args: origin: Origin IATA code. destination: Destination IATA code. departure_at: Departure date (YYYY-MM-DD or YYYY-MM). Optional. return_at: Return date (YYYY-MM-DD or YYYY-MM). Optional. limit: Max results (1-20, default 10). currency: Price currency (3 letters). Defaults to the server's c…
get_city_directionsread-onlyList the cheapest destinations reachable from a city, with a fare and dates. Use when the user asks where they can fly from a city, or wants somewhere cheap without naming a destination. For who flies into a city use `get_popular_directions`; to price one chosen route afterwards use `search_flights` or `get_prices_calendar`. Args: origin: Origin city IATA code (e.g. "MOW"). Use `lookup_cities` to resolve a city name first. currency: Price currency (3 letters). Defaults to the server's currency. Returns: Dict with "status", "currency" and "data" — destination code to chea…
get_flexible_date_pricesread-onlyCompare prices for the days around a departure and an optional return. Use when the user already has dates and asks whether shifting a day either way would be cheaper. For one exact date use `search_flights`; for the cheapest day across a whole month use `get_prices_calendar`. This covers roughly a week around both the outbound and the return. Args: origin: Origin IATA code. destination: Destination IATA code. depart_date: Intended departure date (YYYY-MM-DD). Required. return_date: Intended return date (YYYY-MM-DD). Omit for one-way. currency: Price currency (3 letters).…
get_latest_pricesread-onlyGet the most recently found flight prices from other travellers' searches. Use when the user wants the latest fares that just appeared, on one route or across the whole cache. For a specific trip on chosen dates use `search_flights` instead. Prices are per adult (cached); passenger parameters are encoded into each booking_link. These rows come from the older v2 shape: they name the selling `agency` rather than an airline, carry no flight number, and their booking_link is reconstructed from the route and dates. Args: origin: Origin IATA code. Optional. destination: Destination IATA c…
get_popular_directionsread-onlyList the cities people most often fly to a destination from, with a fare. Use when the user asks where travellers reach a city from and what that costs. The request is keyed on the destination. For where someone can fly from a city use `get_city_directions`; for prices on one known route use `search_flights`. Args: destination: Destination IATA code (e.g. "BKK"). Required — the API rejects a request without it. currency: Price currency (3 letters). Defaults to the server's currency. locale: 2-letter locale for city names. Defaults to the server's locale. Returns: Dic…
get_prices_calendarread-onlyGet grouped calendar prices for a route, one fare per day or per month. Use when the user asks which day or month is cheapest to fly a known route. For fares on one specific date use `search_flights`; for a few days either side of dates already chosen use `get_flexible_date_prices`. Codes are IATA; use `lookup_cities` to resolve a name first. Prices are per adult (cached); passenger parameters are encoded into each booking_link. Args: origin: Origin IATA code. destination: Destination IATA code. departure_at: Departure month (YYYY-MM). Optional. return_at: Return month (YYYY…
lookup_airlinesread-onlyLook up airlines by name or IATA code. Use when the user asks which airline a code belongs to, or wants the IATA code for an airline name. For an airport, city, or country code use `lookup_airports`, `lookup_cities`, or `lookup_countries`; for fares use `search_flights`. Args: search: Airline name substring or exact IATA code (e.g. "aeroflot", "SU"). Omit to list airlines from the start of the dataset. limit: Max results to return (1-500, default 50). locale: 2-letter locale for names (e.g. "en", "ru"). Defaults to the server's locale. Returns: Dict with "sta…
lookup_airportsread-onlyLook up airports by name, IATA code, or city code. Use when the user names an airport or a code and needs its city, country, or coordinates. For the closest airport to a town that does not share the airport's name, use `find_nearest_airports` instead of this tool. The full dataset is ~10k airports, so always pass `search` — an unfiltered call just returns the first `limit` entries in dataset order. Results are ranked: exact code, then exact city code, then name matches, with airports you cannot actually fly to last. Args: search: Airport name substring, exact IATA code, or city code …
lookup_citiesread-onlyLook up cities by name or IATA code and return the code flight tools expect. Use when the user names a city and a flight search needs its IATA code. For an airport code use `lookup_airports`; for the nearest airport to a place that is not itself a city, use `find_nearest_airports`. Every flight tool takes IATA codes, so this is usually the first call when the user names a place. The full dataset is ~9.6k cities, so always pass `search`. Names are only available in the requested locale: searching "Мюнхен" needs locale="ru". Args: search: City name substring or exact IATA code (e.g. "bang…
lookup_countriesread-onlyLook up countries by name or two-letter country code. Use when the user asks which country a code belongs to, or wants that country's code or currency. For a city or airport code use `lookup_cities` or `lookup_airports`; this tool does not search flight prices. Args: search: Country name substring or exact code (e.g. "thailand", "TH"). limit: Max results to return (1-500, default 50). locale: 2-letter locale for names (e.g. "en", "ru"). Defaults to the server's locale. Returns: Dict with "status", "total", "returned", "truncated" and "data" (country objects: code…
search_by_price_rangeread-onlyFind flights whose cached fare falls inside a minimum and maximum price. Use when the user has a budget, including anywhere under a price with no destination named. Leave `destination` unset to let the budget pick the city; prices are per adult in economy. For a named route on a date or a month use `search_flights` or `get_prices_calendar`. There is deliberately no date argument: this endpoint ignores one (verified — passing a December date returns the same July and September fares), and each result carries its own `departure_at`. Args: origin: Origin IATA code. value_min: Lowest ac…
search_flightsread-onlySearch flight prices between two cities on a date or across a month. Use when the user names both ends of a route and wants fares, a booking link, or only departures inside a time window. For the cheapest day in a month use `get_prices_calendar`; for the days around dates already chosen use `get_flexible_date_prices`; for a budget with no destination use `search_by_price_range`. Both codes must be IATA — call `lookup_cities` first if you only have a city name. For nearby airports use `get_alternative_directions`. A multi-city trip needs one call per leg. Note on passengers: the price data c…
Compare and alternatives
Featured in
Signals
- Stars
- 13
- Forks
- 3
- Open issues
- 0
- Weekly downloads
- 70
- Last commit
- Oct 24, 2026 (5 days ago)
- Last release
- Oct 14, 2026 (14 days ago)
- Last package publish
- Oct 14, 2026 (14 days ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.stufently/aviasales-mcp- Version
- 0.5.3
- Auth
- API key
- Packages
- oci
ghcr.io/stufently/aviasales-mcp:0.5.3pypi aviasales-mcp - License
- GPL-3.0
- Repository
- github.com/stufently/aviasales-mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from stufently
- 0.646score
Yandex Webmaster MCP
stufently
MCP server for Yandex Webmaster API — site analytics, indexing, search queries
ConnectorAFreshness: ALocal★ 19Claude Code +5 - 0.646score
Yandex Wordstat MCP
stufently
MCP server for Yandex Wordstat API — keyword research for Russian/CIS markets
ConnectorAFreshness: ALocal★ 19Claude Code +5 - 0.646score
Yandex Metrika MCP
stufently
MCP server for Yandex Metrika API — web analytics, traffic, audience data
ConnectorAFreshness: ALocal★ 19Claude Code +5 - 0.646score
Yandex Direct MCP
stufently
MCP server for Yandex Direct API v5 — campaigns, ads, keywords, reports
ConnectorAFreshness: ALocal★ 19Claude Code +5 - 0.643score
Yandex Search MCP
stufently
MCP server for Yandex Search API (v2, Cloud)
ConnectorAFreshness: ALocalRead-only★ 19Claude Code +5 - 0.637score
Google Webtools MCP
stufently
Google Search Console + GA4 for AI agents: properties, reports, indexing, verification, SEO.
ConnectorAFreshness: ALocal★ 6Claude Code +5
Cite this page
Aviasales Flight Prices MCP server. Agent Mart. https://agentmart.dev/connectors/stufently-aviasales-mcp (last updated 2026-10-24)