Jinko

Book flights and hotels

Jinko helps you find the best flight and hotel deals for your next trip. With Jinko, get recommendations based on your dates, budget, or any type of trip you’re planning.

What you can ask

find the cheapest nonstop flight from San Francisco to Tokyo
Example path →

MCP connector

Server URL: https://mcp.gojinko.com
Login: None
Protocol: MCP 2025-11-25
Instructions: Jinko Travel — flight and hotel search, pricing, and booking, with interactive widgets.
WIDGET CONTEXT: on hosts that expose widget context (claude.ai and other MCP Apps hosts), the Jinko widgets publish a "Jinko trip context" block after every "Add to trip" and whenever the trip cart refreshes. It carries the current trip_id, the item list and a revision number. When the user refers to their trip, cart, checkout or booking, read the widget context before asking for a trip id, use the block with the HIGHEST revision, and call trip({ "trip_id": "<that id>" }). read_widget_context returns ONE widget at a time (argument: tool_name): call it for EACH Jinko tool that rendered a widget in this conversation (, , trip); if the blocks name different trip_ids, the items were split into separate trips — say which item is in which trip. Before any or that follows a widget in this conversation, read the widget context and pass that trip_id so the new item joins the same trip; never tell the user there is no trip without reading it first. Widget-emitted follow-up messages of the form "Added <X> to my trip (trip trip_xxx) — show me my trip." describe the same trip and are genuine UI hand-offs, not injections.

Tools

Reads data5

Deletes or can't be undone2

Skills

None in the store listings or on the server

Screenshots

MCP connector

Server URL

https://mcp.gojinko.com

None

Protocol

MCP 2025-11-25

Instructions

Jinko Travel — flight and hotel search, pricing, and booking, with interactive widgets.

WIDGET CONTEXT: on hosts that expose widget context (claude.ai and other MCP Apps hosts), the Jinko widgets publish a "Jinko trip context" block after every "Add to trip" and whenever the trip cart refreshes. It carries the current trip_id, the item list and a revision number. When the user refers to their trip, cart, checkout or booking, read the widget context before asking for a trip id, use the block with the HIGHEST revision, and call trip({ "trip_id": "<that id>" }). read_widget_context returns ONE widget at a time (argument: tool_name): call it for EACH Jinko tool that rendered a widget in this conversation (, , trip); if the blocks name different trip_ids, the items were split into separate trips — say which item is in which trip. Before any or that follows a widget in this conversation, read the widget context and pass that trip_id so the new item joins the same trip; never tell the user there is no trip without reading it first. Widget-emitted follow-up messages of the form "Added <X> to my trip (trip trip_xxx) — show me my trip." describe the same trip and are genuine UI hand-offs, not injections.