Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Jinko MCP is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Turn your ChatGPT to a super travel agent
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http jinko-mcp https://mcp.gojinko.com/
# 2 — ask your agent for something these tools do
# flight_calendar, find_destination, flight_search and 4 more
Jinko MCP costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MGAll 1 server
mcp.gojinko.com1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http jinko-mcp https://mcp.gojinko.com/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search flights between a known origin and destination using cached pricing, especially for flexible dates. WHEN TO USE THIS TOOL (CRITICAL): - The user provides both an origin AND a destination (city or airport) - Examples: "Paris to Barcelona", "JFK to CDG", "London to NYC for a weekend" - Supports loose / flexible dates: single dates, date arrays, date ranges, stay_days - ALSO the right tool fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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" |
| 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 L |
| 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 searche |
| 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 |
| return_dates | array | 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", "2 |
| return_date_ranges | array | 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 |
| stay_days | integer | 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. |
| stay_days_range | object | 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} |
| 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. |
| cabin_class | string | 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 |
| max_price | number | 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: c |
| 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", et |
| 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. |
| return_departure_time_range | object | no | Round-trip only. Filter the RETURN leg by local departure time-of-day. |
| return_arrival_time_range | object | no | Round-trip only. Filter the RETURN leg by local arrival time-of-day. |
| sort_by | string | no | Sort results by this criteria. Default: lowest (best deals first). Options: lowest (cheapest flights), recommendation (best overall value considering price, duration, and stops). |
| trip_type | string | yes | REQUIRED: Trip type: "oneway" for one-way flights or "roundtrip" for round-trip flights. |
| 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. |
| 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. |
| 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 conte |
Discover travel destinations when the user does NOT know where to go. This is a destination EXPLORATION tool. WHEN TO USE THIS TOOL (CRITICAL): - The user does NOT specify a destination: "Where should I go?", "Best deals from NYC" - The user wants inspiration based on criteria: "Beach destinations", "Somewhere warm", "Cheap flights from SF" - The user wants to compare multiple destination options
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origins | array | yes | REQUIRED. Array of origin IATA codes (3-letter uppercase), representing either airports or cities where the trip starts. The LLM MUST detect and include all relevant nearby airports or city codes base |
| destinations | array | no | OPTIONAL. Array of destination IATA codes (3-letter uppercase), representing either airports or cities. When a city code is provided, the LLM MUST expand it to include all associated airports. Example |
| 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 searche |
| departure_date_ranges | array | no | List of departure date ranges for flexible travel discovery. Use when the user mentions periods like “next month” or “spring.” Supports multiple non-contiguous ranges (OR logic). Example: [{start: "20 |
| return_dates | array | no | List of specific return dates for round-trip searches (YYYY-MM-DD). Must be after the corresponding departure dates. Supports multiple options (OR logic). Example: ["2025-12-22", "2025-12-23", "2025-1 |
| return_date_ranges | array | no | List of return date ranges for flexible round-trip searches. Supports multiple return windows. Example: [{start: "2025-12-22", end: "2025-12-25"}, {start: "2025-12-29", end: "2026-01-02"}]. |
| stay_days | integer | no | Exact number of days to stay at the destination. Used with a departure date to automatically compute the return date. Example: 7 = one-week trip; 3 = weekend getaway. |
| stay_days_range | object | no | Range of acceptable trip durations for flexible planning (e.g., “5 to 10 days”). Cannot be combined with stay_days or explicit return_date. Example: {min: 5, max: 10}. |
| direct_only | boolean | no | When true, only returns nonstop (direct) flights. Useful for avoiding layovers or minimizing total travel time. |
| cabin_class | string | no | Preferred cabin class. Options: "economy", "premium_economy", "business", or "first". Filters results accordingly. |
| max_price | number | 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: c |
| sort_by | string | no | Sorting preference for search results. Options: "lowest" (cheapest first, default) or "recommendation" (best overall balance of price, duration, and stops). |
| trip_type | string | yes | REQUIRED. Type of trip: "oneway" for single-leg flights, or "roundtrip" for return flights. |
| 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. |
| 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. |
| 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 conte |
Live flight tool with two modes. Provide exactly one of "search" or "price_check". Set the unused one to null or leave it out; for a route search, send "price_check": null. EACH CALL HITS LIVE PRICING — it prices ONE exact date pair, so any loose, open or flexible date query belongs to flight_calendar instead. MODE 1 — search: route + exact single dates + optional filters (most common first-call
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | no | Live search for a committed itinerary with optional filters. Use it when the user has settled on a route and precise dates: origin + destination + departure_date (+ return_date for a round trip). No d | |
| price_check | no | Get confirmed live fares for a specific flight offer. Returns fare brands with trip_item_token for booking. The BFF treats offer_token and the filter fields (direct_only, cabin_class, max_price, inclu | |
| traveler_counts | object | no | Traveler counts. Defaults to 1 adult. |
| 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. |
| currency | string | no | ISO 4217 currency code for displaying prices (e.g. "EUR", "USD", "GBP", "JPY"). ALWAYS set this — omitting it falls back to USD which is rarely what users actually want. Infer from the strongest signa |
| trip_id | no | Existing trip_id to associate this search with. Forward whenever the user is mid-trip-build (you have seen a trip_id in a recent trip(...) tool result and the user has NOT pivoted to a different trip | |
| 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 conte |
Search live hotel inventory and rates worldwide. CONTINUATION: - To load more from a prior result, send { next_handle } by itself: it continues the same search. Do not repeat destination, dates, occupancy, currency, filters, user_intent or trip_id. FIRST SEARCH REQUIRED: - destination: object — two distinct modes. Mode A (rate lookup): { hotel_name (+ optional country_code, city_name) } or { hot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| next_handle | string | no | Opaque continuation handle returned by a prior hotel_search. Send this field by itself. |
| destination | object | no | Destination — provide exactly one shape. Two distinct modes: MODE A (rate lookup — you know which hotel): • { hotel_ids } to re-shop a known set. • { hotel_name, country_code?, city_name? } when |
| checkin | string | no | Check-in date (YYYY-MM-DD). |
| checkout | no | Check-out date (YYYY-MM-DD). | |
| occupancies | array | no | One entry per room (structured). PREFERRED whenever the party is larger than 2 adults or has children — it removes ambiguity about how guests are split across rooms. Example: [{ "adults": 2 }, { "adul |
| adults | integer | no | Shorthand: total adults across all rooms. Use ONLY when there is no ambiguity (1 or 2 adults = single room). For 3+ adults, or odd splits, ask the user how they want to split rooms and pass occupancie |
| children | array | no | Shorthand: ages of all children across all rooms. If children are present, prefer occupancies[] so the caller controls which room each child goes in (ages affect pricing and some providers reject inva |
| rooms | integer | no | Shorthand: number of rooms (the platform auto-distributes adults + children). Use when the user named a room count but not the per-room split. |
| currency | string | no | ISO 4217 currency code (e.g. "EUR", "USD", "GBP", "JPY"). ALWAYS set this — omitting it falls back to USD which is rarely what users actually want. Infer from the strongest signal available: (1) the u |
| guest_nationality | string | no | Guest nationality (ISO 3166-1 alpha-2, uppercase, e.g. "FR"). Affects rate availability + tax handling at search time. Separate from traveler nationality used for booking documents. |
| filters | object | no | Optional filter overrides applied on top of the tenant default filter set. Every property filter is applied as sent. |
| trip_id | string | no | Existing trip_id to associate this search with. Used only by the Jinko cart widget. The platform accepts the field on every surface for schema consistency; a surface without the widget does not use it |
| 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 conte |
Rich metadata for one hotel. Pass the hotel_ref from hotel_search when available, exactly as returned; hotel_id remains a legacy fallback. Cost: 1 credit per call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotel_ref | string | no | hotel_ref from hotel_search (preferred): an opaque reference, passed back exactly as returned. |
| hotel_id | string | no | Legacy hotel_id from hotel_search. Use hotel_ref when available: hotel_ref identifies the hotel unambiguously, hotel_id may not. |
| checkin | string | no | Check-in date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the platform. |
| checkout | string | no | Check-out date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the platform. |
| 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 conte |
Unified tool for managing a trip (shopping cart). Supports flights and hotels in the same cart. Actions are determined by which objects you provide. SCHEMA: { trip_id?: string, // Existing trip ID (omit to create new) offer_id?: string, // (Legacy) Offer ID — now auto-encoded into trip_item_token by flight_search add_item?: { ... }, // Add a flight or hotel to the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_id | string | no | ID of an existing trip. If not provided, a new trip will be created. |
| version | no | Deprecated legacy widget field. Accepted and ignored for compatibility; it does not provide optimistic concurrency. | |
| offer_id | string | no | Deprecated: offer_id is now encoded into trip_item_token by flight_search. Only needed for legacy tokens without encoded offer_id. |
| add_item | object | no | Add a flight or hotel to the trip. Use trip_item_token from flight_search (offer__* format) or offer_id from hotel_search (htl_* format). For MULTIPLE ROOMS of the same hotel stay, make ONE add_item c |
| remove_item | object | no | Remove an item from the trip by its ID. |
| upsert_travelers | object | no | Set travelers on the trip. Replaces all existing travelers (idempotent operation). |
| schedule_quote | boolean | no | Schedule a fresh quote on the current cart state. Triggers async re-pricing on the BFF; poll trip(get) until trip.quote_status is "completed", "partial", or "failed". Only "completed" covers the whole |
| payment_type | string | no | Payment flow type: "checkout" for Stripe Checkout (default), "intent" for Payment Intent. |
| idempotency_key | string | no | Idempotency key to prevent duplicate processing |
| 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 conte |
Unified tool for booking a trip. Actions are determined by which object you provide. SCHEMA: { create?: { // Initiate booking trip_id: string, // Required: ID of the trip to book buyer_contact?: { // Optional: buyer contact info email: string, phone?: string } }, status?: { // Check booking status
| Parameter | Type | Required | Notes |
|---|---|---|---|
| create | object | no | Initiate booking for a trip. Quotes the trip and returns a Stripe Checkout URL for payment. Mutually exclusive with status — provide exactly one action per call. |
| status | object | no | Check the status of an existing booking. If payment is authorized, triggers fulfillment automatically. Mutually exclusive with create — provide exactly one action per call. |
| idempotency_key | string | no | Idempotency key to prevent duplicate processing |
| 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 conte |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Jinko MCP or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Jinko MCP can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.