Skip to main content
The Jinko MCP server plugs travel straight into your AI agent. Connect a client like Claude or Cursor over OAuth (or a bearer API key), and it can search flights and hotels, build a trip, pay, and manage bookings right inside a conversation, with no custom integration to write. New to this? Start with Connect over MCP to set up your client. The tools are grouped by what they do (below), and each page lists its input schema, parameters, and examples.

​
Endpoint

EnvironmentEndpoint
Productionhttps://mcp.builders.gojinko.com/mcp
Sandboxhttps://mcp.builders.sandbox.gojinko.com/mcp
Production is the default. Use sandbox to run the full flow against isolated data. It uses separate API keys / OAuth (see Sandbox keys). A production token will not authenticate against sandbox, and vice-versa.

​
Authentication

Most modern MCP clients connect over OAuth: give them the endpoint URL and approve the flow. When a client doesn’t support OAuth, attach your API key as a bearer token instead: 
Authorization: Bearer jnk_your_key
See Connect over MCP for client-specific setup (Claude Code, Cursor, and more).

​
Tool groups

Flights

Discover routes and dates, run a live search, then handle refunds and exchanges: find_destination, flight_calendar, find_dates, lowest_fare, price_monitoring, flight_search, flight_refund, flight_exchange.

Hotels

Search hotels and pull details; results drop into the same trip as flights: hotel_search, hotel_details, hotel_cancel.

Cart & Payment

Build a trip, check out, pay via a browser link or a Shared Payment Token, and look up the booking: trip, checkout, submit_agent_payment, get_trip, get_booking.