About Jinko MCP
Turn your ChatGPT into a super travel agent
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
Endpoint
https://mcp.gojinko.comCopy install command
Claude CodeTerminal
claude mcp add --transport http com-gojinko-mcp-jinko https://mcp.gojinko.comCursor.cursor/mcp.json
{"mcpServers":{"com-gojinko-mcp-jinko":{"type":"http","url":"https://mcp.gojinko.com"}}}Open in CursorVS Code.vscode/mcp.json
{"servers":{"com-gojinko-mcp-jinko":{"type":"http","url":"https://mcp.gojinko.com"}}}Open in VS CodeClaude Desktopclaude_desktop_config.json
{"mcpServers":{"com-gojinko-mcp-jinko":{"type":"http","url":"https://mcp.gojinko.com"}}}Windsurf~/.codeium/windsurf/mcp_config.json
{"mcpServers":{"com-gojinko-mcp-jinko":{"serverUrl":"https://mcp.gojinko.com"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
All endpoints
Streamable HTTP
https://mcp.gojinko.comSSE
https://mcp.gojinko.comTools
7| Parameter | Type | Required | Description |
|---|---|---|---|
| locale | string | No | User's BCP 47 locale inferred from the conversation (e.g. "fr-FR", "en-US", "ja-JP"). Used for formatting dates, numbers, and selecting currency. Infer from the user's language and location context. |
| origin | string | Yes | REQUIRED: Single origin IATA airport code or IATA city code. Airport codes: "JFK" for John F. Kennedy in New York, "LGW" for Gatwick in London. City codes: "NYC" for New York, "LON" for London, "PAR" for Paris. A code that names a multi-airport city (NYC, LON, PAR — and LAX, MIA, LAS, which a city shares with its main airport) covers every airport of that city; any other code is that one airport. |
| sort_by | enum | No | Sort results by this criteria. Default: lowest (best deals first). Options: lowest (cheapest flights), recommendation (best overall value considering price, duration, and stops).lowest | recommendation |
| currency | string | No | ISO 4217 currency code for displaying prices (e.g. "EUR", "USD", "GBP"). Infer from the user's country or locale. If the user mentions a specific currency, use that. |
| max_price | any | No | Maximum price PER PERSON: the cap applies to a one-adult fare, in the requested currency. For a whole-party budget, divide it by the number of ADULTS only and treat the result as a loose pre-filter: children and lap infants usually cost less than an adult, so dividing by every traveller would exclude affordable trips. Send a per-person budget as-is. The exact whole-trip budget check is flight_search with max_price. |
| stay_days | any | No | Exact number of days to stay at destination. Used with departure_date to calculate return date automatically. Example: 7 for a week-long trip, 3 for a weekend getaway. |
| trip_type | enum | Yes | REQUIRED: Trip type: "oneway" for one-way flights or "roundtrip" for round-trip flights.oneway | roundtrip |
| cabin_class | any | No | Cabin class preference. Options: "economy" (standard economy), "premium_economy" (enhanced economy with more space/amenities), "business" (business class), "first" (first class). When specified, only shows flights in the requested cabin class. |
| destination | string | Yes | REQUIRED: Single destination IATA airport code or IATA city code. Airport codes: "CDG" for Paris Charles de Gaulle, "SFO" for San Francisco. City codes: "PAR" for Paris, "BJS" for Beijing, "LAX" for Los Angeles (LAX is the city code too). A code that names a multi-airport city (NYC, LON, PAR — and LAX, MIA, LAS, which a city shares with its main airport) covers every airport of that city; any other code is that one airport. |
| direct_only | boolean | No | Only show direct/nonstop flights. When true, only flights with no stops are returned. Use for fastest travel or when layovers are not desired. |
| user_intent | string | No | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and context to improve the overall user experience. - For short, self-contained prompts (e.g. "I want new shoes"), copy the user message as-is. - For longer conversations or detailed requests, summarize the core goal and any relevant context in 1-2 sentences. Focus on intent, constraints, and preferences - not the full dialogue. Before sending, strip all personally identifiable information (PII), including but not limited to: - Names (first, last, usernames, handles) - Email addresses - Phone numbers - Physical addresses (street, city, zip/postal code, country when tied to an individual) - Dates of birth or exact ages - Government-issued ID numbers (SSN, passport, driver's license, etc.) - Payment or financial information (card numbers, bank accounts, etc.) - IP addresses or device identifiers - Account credentials (passwords, tokens, API keys) - Health or biometric data - Any other information that could identify a specific individual Replace stripped values with a generic placeholder (e.g. "[name]", "[email]", "[address]"). Examples: User: "I want red running shoes under $100" -> "I want red running shoes under $100" User: "Hi, I'm John Smith, [email protected], and I'm looking for flights from Paris to Tokyo for 2 adults departing around mid-June, budget around EUR2000 total" -> "Looking for flights from Paris to Tokyo for 2 adults, mid-June, budget ~EUR2000" User: "I need help resetting my password for account ID acct_12345" -> "I need help resetting my password for account ID [account_id]" |
| return_dates | any | No | List of specific return dates for round-trip flights (YYYY-MM-DD). Use for searching multiple return date options with OR logic. Must be after departure dates. Example: ["2025-12-22", "2025-12-23", "2025-12-24"] |
| departure_dates | array | No | List of specific departure dates in ISO 8601 format (YYYY-MM-DD). Use for searching multiple specific dates with OR logic. Example: ["2025-12-15", "2025-12-16", "2025-12-17"] for flexible date searches. Useful when user wants to check specific dates like weekends. |
| stay_days_range | any | No | Flexible stay duration range. Use when user wants flexibility in trip length (e.g., "5 to 10 days"). Cannot be combined with exact stay_days or return_date. Example: {min: 5, max: 10} |
| arrival_time_range | object | No | Filter the OUTBOUND leg by local arrival time-of-day. Example: { "latest": "20:00" } to arrive by 8pm. Use when the user says "arrive before dinner", "land by noon", etc. |
| arrival_time_range.latest | string | No | Inclusive latest local time-of-day (HH:MM, 24-hour). |
| arrival_time_range.earliest | string | No | Inclusive earliest local time-of-day (HH:MM, 24-hour). |
| return_date_ranges | any | No | List of return date ranges for flexible round-trip exploration. Use when user wants flexibility on return timing across multiple periods with OR logic. Example: [{start: "2025-12-22", end: "2025-12-25"}, {start: "2025-12-29", end: "2026-01-02"}] |
| departure_time_range | object | No | Filter the OUTBOUND leg by local departure time-of-day. Example: { "earliest": "08:00", "latest": "12:00" } for a late-morning departure. Use when the user says "morning flight", "leave after 6pm", etc. |
| departure_time_range.latest | string | No | Inclusive latest local time-of-day (HH:MM, 24-hour). |
| departure_time_range.earliest | string | No | Inclusive earliest local time-of-day (HH:MM, 24-hour). |
| departure_date_ranges | array | No | List of departure date ranges for flexible travel exploration. Use when user says "next month", "spring", or wants to discover deals across multiple date periods with OR logic. Example: [{start: "2025-12-10", end: "2025-12-15"}, {start: "2025-12-20", end: "2025-12-25"}] for non-contiguous periods. |
| return_arrival_time_range | any | No | Round-trip only. Filter the RETURN leg by local arrival time-of-day. |
| return_departure_time_range | any | No | Round-trip only. Filter the RETURN leg by local departure time-of-day. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
Markdown supported
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.