Skip to directory

About Jinko MCP

Jinko provides a hosted travel MCP for searching flights, hotels, and rental cars, assembling bookings into a trip, paying, and managing reservations.

What you can use it for

  • Find travel destinations and flexible dates based on a route or budget
  • Search and compare live flight, hotel, and rental car options
  • Build and manage a multi-item trip and complete checkout
  • Service existing bookings, including eligible cancellations, refunds, and exchanges
Connection and setup
Hosting
Remote, vendor-hosted
Transport
Streamable HTTP
Endpoint
https://mcp.builders.gojinko.com/mcp
Authentication
Production supports OAuth 2.1 with PKCE through browser sign-in for OAuth/DCR-capable MCP clients, or an API key sent as Authorization: Bearer <key>. Sandbox endpoint https://mcp.builders.sandbox.gojinko.com/mcp uses a sandbox API key and does not support OAuth.

Requirements

  • Jinko account; production API key can be created in the Jinko dashboard or OAuth sign-in can create/authorize access
  • For sandbox, enable Sandbox mode and create a separate sandbox key; production and sandbox keys are not interchangeable
  • Usage is metered with plan-based credits/rate limits; the current Free plan is documented as $5 monthly credit, subject to change

Setup steps

  1. For OAuth-capable client, add https://mcp.builders.gojinko.com/mcp as a remote Streamable HTTP MCP server and complete the browser-based Jinko sign-in/consent flow.
  2. If client does not support MCP OAuth, create an API key in the Jinko dashboard and configure Authorization: Bearer <JINKO_API_KEY>; keep the secret in the client's local secret/environment settings.
  3. For isolated tests, use https://mcp.builders.sandbox.gojinko.com/mcp and a sandbox-only API key.
  4. Reload the client if required and confirm the tool catalog loads. Use a read-only search tool for a harmless check; booking, payment, cancellation, refund, and exchange operations may affect real reservations and require explicit user confirmation.
Tools 16

The current Jinko docs record 16 travel search, booking, payment, and trip-management tools. These are retained as the official tool catalog; flight exchanges/refunds, checkout, and payment submission are consequential booking/account operations. Production and sandbox use separate endpoints and auth rules.

  • find_destination

    Discover destinations reachable from departure airports.

    01
  • flight_calendar

    Search flights on a route across flexible dates.

    02
  • price_monitoring

    Monitor prices for a route and date pair.

    03
  • flight_search

    Search live flight prices or re-price an offer.

    04
  • flight_refund

    Cancel a booked flight and process refund/void where eligible.

    05
  • flight_exchange

    Exchange a booked flight for a different itinerary.

    06
  • hotel_search

    Search hotel availability and rates.

    07
  • hotel_details

    Retrieve hotel details, photos, facilities, and policies.

    08
  • hotel_cancel

    Cancel a hotel booking; documentation describes preview/commit behavior.

    09
  • car_search

    Search rental car availability and offers.

    10
  • car_cancel

    Cancel a car rental with cancellation fee shown first.

    11
  • trip

    Create and manage a trip, items, travelers, and ancillaries.

    12
  • checkout

    Check out a trip and return a payment/checkout flow.

    13
  • submit_agent_payment

    Submit a Shared Payment Token for server-side payment authorization.

    14
  • get_trip

    Retrieve trip lifecycle state, items, travelers, quote, and fulfillment.

    15
  • get_booking

    Look up a booking and identify servicing options.

    16
Limitations and notes
  • Tools are subject to account permissions, plan credits, provider availability, and service rate limits.
  • Production and sandbox use distinct endpoints and API keys; sandbox has no OAuth.
  • Booking, payment, cancellation, refund, and exchange tools can cause consequential external actions; preview/confirmation flows apply where documented.
  • Tool results may expose structuredContent and text summary channels; official docs warn clients not to parse the summary text as JSON.
Original sources
  • official complete tool catalog

    Publisher tool overview enumerates 16 exact tools across flights, hotels, rental cars, and trip/payment operations.

  • official setup guide

    Jinko documents Streamable HTTP, production/sandbox hosts, OAuth or bearer-key auth and client configuration.

  • official authentication guide

    Publisher describes OAuth 2.1 with PKCE/DCR, API key setup, environment separation and current usage credits.

Documentation checked 2026-10-28T14:00:00.000Z. Connection has not been runtime tested.

Similar tools