Jinko Flight Search
Search flights and discover destinations via the Jinko MCP server (find_destination and find_flight tools).
MCP Connection
Connect the Jinko MCP server in Claude's settings or project integrations using this URL:
https://mcp.gojinko.com
This provides two tools: Jinko:find_destination and Jinko:find_flight.
Tool Selection
- User knows origin AND destination city → Use
find_flight
- User wants destination ideas, doesn't know where to go, or specifies criteria (beach, warm, ski, cheap…) → Use
find_destination
- User asks for the cheapest dates to a single known destination → Use
find_flight
Tool 1: find_destination — Discover Where to Go
Use when the user is exploring options and hasn't committed to a single destination city.
Required Parameters
origins — Array of IATA codes for ALL nearby airports at the user's origin.trip_type — "roundtrip" (default) or "oneway" (only when user explicitly says one-way).
Optional Parameters
| Parameter |
Use when |
destinations |
User mentions a region, criteria, or list of candidate cities. Generate IATA codes matching the intent. Leave empty for global discovery ("anywhere", "surprise me"). |
departure_dates / departure_date_ranges |
User specifies dates or periods. All dates MUST be in the future. |
return_dates / return_date_ranges |
User specifies return windows. |
stay_days / stay_days_range |
User mentions trip length ("a week", "5-10 days"). |
max_price |
User mentions a budget. |
direct_only |
User asks for nonstop/direct flights. |
cabin_class |
"economy", "premium_economy", "business", or "first". |
currency |
ISO 4217 code matching user's locale. |
locale |
e.g. "en-US", "fr-FR". |
sort_by |
"lowest" (default) or "recommendation". |
Airport Identification — Critical
Always expand a city to ALL its airports:
- New York →
["JFK","LGA","EWR"]
- London →
["LHR","LGW","STN","LTN","LCY"]
- Paris →
["CDG","ORY"]
- Tokyo →
["NRT","HND"]
- Chicago →
["ORD","MDW"]
- Los Angeles →
["LAX"]
- San Francisco / SFO →
["SFO"]
Destination Generation — Critical
When users describe criteria, generate matching IATA codes before calling the tool:
- "Beach" →
["MIA","SAN","HNL","CUN","PUJ","SJU","NAS","MBJ"]
- "Asia" →
["NRT","HND","ICN","PVG","PEK","HKG","SIN","BKK","KUL","MNL"]
- "European capitals" →
["LHR","CDG","FRA","MAD","FCO","AMS","BRU","VIE","PRG","CPH"]
- "Ski" →
["DEN","SLC","ZRH","INN","GVA","TRN"]
- "Warm in winter" →
["MIA","MCO","SAN","PHX","HNL","CUN","PUJ","PTY","LIM","GIG"]
When to Re-call
Re-call find_destination when the user changes destination criteria, dates, or asks to explore different options — especially when they are already viewing the widget in fullscreen.
Examples
| User says |
origins |
destinations |
other params |
| "Where should I travel from NYC next month?" |
["JFK","LGA","EWR"] |
[] (global) |
departure_date_ranges for next month |
| "Cheap flights from SF to Europe under $800" |
["SFO"] |
European airports |
max_price: 800 |
| "Somewhere warm from Chicago, 1 week in Dec" |
["ORD","MDW"] |
warm-weather airports |
stay_days: 7, Dec date range |
| "Best weekend getaways from Boston" |
["BOS"] |
[] (global) |
stay_days_range: {min:2, max:4} |
Tool 2: find_flight — Search a Specific Route
Use when both origin and destination cities are known.
Required Parameters
origin — Single IATA airport or city code (e.g. "JFK", "PAR").destination — Single IATA airport or city code (e.g. "CDG", "LON").trip_type — "roundtrip" (default) or "oneway".
Optional Parameters
Same date, stay, price, cabin, currency, locale, direct, and sort parameters as find_destination.
Examples
| User says |
origin |
destination |
other params |
| "Flights from JFK to CDG next month" |
"JFK" |
"CDG" |
departure_date_ranges for next month |
| "LA to Tokyo for a week in December" |
"LAX" |
"TYO" |
stay_days: 7, Dec date range |
| "Business class NYC to London, 5-10 days" |
"NYC" |
"LON" |
cabin_class: "business", stay_days_range: {min:5, max:10} |
| "Cheapest ORD to LHR under $600" |
"ORD" |
"LHR" |
max_price: 600 |
General Rules
- Default to roundtrip. Only use
"oneway" when the user explicitly writes "one way" or "one-way".
- All dates must be in the future. Never send a past date.
- Fill as many search parameters as possible from the user's intent to get the best results.
- Use city codes (e.g.
"LON", "NYC", "PAR", "TYO") when searching across all airports in a city.
- Provide results in the user's preferred currency and locale when identifiable.
1---2name: jinko-flight-search3description: Search flights and discover travel destinations using the Jinko MCP server. Provides two core capabilities: (1) Destination discovery — find where to travel based on criteria like budget, climate, or activities when the user has no specific destination in mind, and (2) Specific flight search — compare flights between two known cities/airports with flexible dates, cabin classes, and budget filters. Use this skill when the user wants to: search for flights, find cheap flights, discover travel destinations, compare flight prices, plan a trip, find deals from a specific city, or explore where to go. Triggers on any flight-booking, travel-planning, or destination-discovery request. Requires the Jinko MCP server connected at https://mcp.gojinko.com.4---5
6# Jinko Flight Search
7
8Search flights and discover destinations via the Jinko MCP server (`find_destination` and `find_flight` tools).
9
10## MCP Connection
11
12Connect the Jinko MCP server in Claude's settings or project integrations using this URL:
13
14```
15https://mcp.gojinko.com
16```
17
18This provides two tools: `Jinko:find_destination` and `Jinko:find_flight`.
19
20## Tool Selection
21
221. **User knows origin AND destination city** → Use `find_flight`
232. **User wants destination ideas, doesn't know where to go, or specifies criteria (beach, warm, ski, cheap…)** → Use `find_destination`
243. **User asks for the cheapest dates to a single known destination** → Use `find_flight`
25
26## Tool 1: `find_destination` — Discover Where to Go
27
28Use when the user is exploring options and hasn't committed to a single destination city.
29
30### Required Parameters
31
32- `origins` — Array of IATA codes for ALL nearby airports at the user's origin.
33- `trip_type` — `"roundtrip"` (default) or `"oneway"` (only when user explicitly says one-way).
34
35### Optional Parameters
36
37| Parameter | Use when |
38|---|---|
39| `destinations` | User mentions a region, criteria, or list of candidate cities. Generate IATA codes matching the intent. Leave empty for global discovery ("anywhere", "surprise me"). |
40| `departure_dates` / `departure_date_ranges` | User specifies dates or periods. All dates MUST be in the future. |
41| `return_dates` / `return_date_ranges` | User specifies return windows. |
42| `stay_days` / `stay_days_range` | User mentions trip length ("a week", "5-10 days"). |
43| `max_price` | User mentions a budget. |
44| `direct_only` | User asks for nonstop/direct flights. |
45| `cabin_class` | `"economy"`, `"premium_economy"`, `"business"`, or `"first"`. |
46| `currency` | ISO 4217 code matching user's locale. |
47| `locale` | e.g. `"en-US"`, `"fr-FR"`. |
48| `sort_by` | `"lowest"` (default) or `"recommendation"`. |
49
50### Airport Identification — Critical
51
52Always expand a city to ALL its airports:
53
54- New York → `["JFK","LGA","EWR"]`
55- London → `["LHR","LGW","STN","LTN","LCY"]`
56- Paris → `["CDG","ORY"]`
57- Tokyo → `["NRT","HND"]`
58- Chicago → `["ORD","MDW"]`
59- Los Angeles → `["LAX"]`
60- San Francisco / SFO → `["SFO"]`
61
62### Destination Generation — Critical
63
64When users describe criteria, generate matching IATA codes before calling the tool:
65
66- "Beach" → `["MIA","SAN","HNL","CUN","PUJ","SJU","NAS","MBJ"]`
67- "Asia" → `["NRT","HND","ICN","PVG","PEK","HKG","SIN","BKK","KUL","MNL"]`
68- "European capitals" → `["LHR","CDG","FRA","MAD","FCO","AMS","BRU","VIE","PRG","CPH"]`
69- "Ski" → `["DEN","SLC","ZRH","INN","GVA","TRN"]`
70- "Warm in winter" → `["MIA","MCO","SAN","PHX","HNL","CUN","PUJ","PTY","LIM","GIG"]`
71
72### When to Re-call
73
74Re-call `find_destination` when the user changes destination criteria, dates, or asks to explore different options — especially when they are already viewing the widget in fullscreen.
75
76### Examples
77
78| User says | origins | destinations | other params |
79|---|---|---|---|
80| "Where should I travel from NYC next month?" | `["JFK","LGA","EWR"]` | `[]` (global) | `departure_date_ranges` for next month |
81| "Cheap flights from SF to Europe under $800" | `["SFO"]` | European airports | `max_price: 800` |
82| "Somewhere warm from Chicago, 1 week in Dec" | `["ORD","MDW"]` | warm-weather airports | `stay_days: 7`, Dec date range |
83| "Best weekend getaways from Boston" | `["BOS"]` | `[]` (global) | `stay_days_range: {min:2, max:4}` |
84
85## Tool 2: `find_flight` — Search a Specific Route
86
87Use when both origin and destination cities are known.
88
89### Required Parameters
90
91- `origin` — Single IATA airport or city code (e.g. `"JFK"`, `"PAR"`).
92- `destination` — Single IATA airport or city code (e.g. `"CDG"`, `"LON"`).
93- `trip_type` — `"roundtrip"` (default) or `"oneway"`.
94
95### Optional Parameters
96
97Same date, stay, price, cabin, currency, locale, direct, and sort parameters as `find_destination`.
98
99### Examples
100
101| User says | origin | destination | other params |
102|---|---|---|---|
103| "Flights from JFK to CDG next month" | `"JFK"` | `"CDG"` | `departure_date_ranges` for next month |
104| "LA to Tokyo for a week in December" | `"LAX"` | `"TYO"` | `stay_days: 7`, Dec date range |
105| "Business class NYC to London, 5-10 days" | `"NYC"` | `"LON"` | `cabin_class: "business"`, `stay_days_range: {min:5, max:10}` |
106| "Cheapest ORD to LHR under $600" | `"ORD"` | `"LHR"` | `max_price: 600` |
107
108## General Rules
109
110- Default to **roundtrip**. Only use `"oneway"` when the user explicitly writes "one way" or "one-way".
111- All dates **must be in the future**. Never send a past date.
112- Fill as many search parameters as possible from the user's intent to get the best results.
113- Use city codes (e.g. `"LON"`, `"NYC"`, `"PAR"`, `"TYO"`) when searching across all airports in a city.
114- Provide results in the user's preferred currency and locale when identifiable.
modbender