Jinko MCP

Installation

Connect an OAuth-capable MCP client to https://mcp.builders.gojinko.com/mcp.

If your client does not support OAuth, use a Jinko API key as a bearer token: Authorization: Bearer jnk_*.

Configuration

• Production MCP endpoint: https://mcp.builders.gojinko.com/mcp
• Sandbox MCP endpoint: https://mcp.builders.sandbox.gojinko.com/mcp
• OAuth is supported for modern MCP clients via the remote endpoint.
• API key mode is supported for clients that cannot do OAuth.
• Production and sandbox use separate keys and OAuth state.

Capabilities

Search flights and hotels, price itineraries, build trips, add travelers and ancillaries, checkout, look up bookings, manage refunds and exchanges, and work with webhooks.

Limitations

• Sandbox and production are isolated; tokens and keys are not interchangeable.
• CLI OAuth tokens are not interchangeable with MCP bearer tokens.
• Search and price offers are time-sensitive and should be refreshed before booking.
• Some refund flows may require manual processing.