Scheduling & Booking · Jinko + Claude
Jinko MCP with Claude: Search, Book and Manage Travel Through One Connection
The short answer
Claude works with Jinko through the Model Context Protocol (MCP), an open standard that lets Claude securely use software with permissions you control. Once connected with an API key, Claude can search flights and hotels, create and modify bookings, manage ancillaries and handle hosted checkout, all through plain-language instructions.
What is Jinko?
Jinko is a travel API platform. It brings flight and hotel discovery, trip management, ancillary services and hosted checkout together in one interface. Travel technology teams, booking businesses, corporate travel functions and operations staff use it to build and run travel search and reservation processes without stitching together many separate systems.
How Claude connects to Jinko through MCP
The Model Context Protocol is an open standard that acts like a universal adapter between Claude and other software. It lets Claude read information from a tool and take actions in it, using a connection your organisation sets up and controls. Jinko's MCP server, or a secure managed connector where needed, provides that link.
Once connected, Claude can typically search for flights and hotels, look up trip details, create and change bookings, and add or manage ancillaries such as extra services. It can also start a hosted checkout. Staff describe what they need in ordinary language, and Claude carries out the steps inside Jinko.
Access is granted with the API key Jinko supports, using least-privilege permissions so Claude only reaches what the role needs. Consequential actions such as confirming or changing a booking can require a person's approval before they run, and every action is recorded in audit logs so your team stays in charge.
What you can automate
Corporate travel requests
Employees describe a trip in plain language, such as dates, route and budget. Claude searches flight and hotel options in Jinko, shortlists those that match your travel policy and presents them to the traveller or travel desk for approval before any booking is made.
Booking changes and cancellations
When a flight is rescheduled or a meeting moves, Claude can review the affected reservations, suggest modifications and prepare the changes. A travel coordinator approves each one, which reduces manual lookups and missed updates.
Ancillary upsell management
Claude can identify relevant ancillaries, such as seat selection, baggage or extra services, for a given booking and prepare offers for the customer. Staff review the offers before they are added, helping support teams handle add-ons consistently.
Hosted checkout support
For customer-facing booking sites or agents, Claude can guide a traveller through search results and direct them to Jinko's hosted checkout. This lets operations teams answer common questions quickly while payment and confirmation stay in the hosted flow.
Trip reporting for finance
Claude can gather booking records and summarise spend by department, route or period from Jinko. Finance teams receive a clear overview that they can check against their own systems, saving time at month-end.
An end-to-end workflow: Employee trip booking with expense sync
TriggerAn employee submits a travel request form in Microsoft 365 for a client visit.
Claude reads the request and checks the dates, destination and budget against the travel policy.
Claude searches flights and hotels through Jinko and ranks the options that fit the policy.
The traveller and their manager receive the shortlist and approve one option.
Claude creates the booking in Jinko, adds any approved ancillaries and sends the confirmation details.
The trip cost and booking reference are logged in the company's finance system for expense tracking.
OutcomeTravel requests move from submission to confirmed booking faster, with policy checks and approvals in place and expense records created automatically. Results vary by organisation and process.
How we set it up
Free automation audit
We review how your team currently handles travel search, bookings, changes and reporting, and identify the workflows worth automating first.
Secure connection
We connect Claude to Jinko using the API key method, with least-privilege access and credentials stored securely under your control.
Workflow design
We map the end-to-end process across Jinko and your other systems such as Microsoft 365, CRM, ERP or ticketing, and decide which actions need human approval.
Testing against real cases
We test the workflow using past bookings and changes from your own records, then refine the prompts and approval steps until the results meet your standards.
Launch, monitoring and training
We launch with monitoring and audit logs in place, then train your travel and operations teams to use and oversee the workflow with confidence.
Who benefits
- Travel managers
- Faster handling of trip requests and changes, with policy checks built into each search and approval.
- Operations heads
- Fewer manual steps across booking, ancillaries and follow-up, and clearer visibility of what has been booked.
- IT and technology leaders
- A controlled, auditable connection that uses an established standard and least-privilege access.
- Finance teams
- Accurate booking records and spend summaries that are easier to reconcile at period end.
Security and control
- Least-privilege access so Claude can only reach the Jinko functions each role requires.
- Human approval for consequential actions such as confirming, changing or cancelling bookings.
- Audit logs of every action Claude takes in Jinko, supporting review and accountability.
- Secure handling of the API key, with rotation and access reviews built into the process.
- Testing against real cases before launch, with ongoing monitoring after go-live.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can run this workflow under their existing data protection rules. Companies in India must meet the Digital Personal Data Protection Act, 2023, while those in the UAE and Saudi Arabia must follow their local data protection laws. We choose the hosting region for any custom application to help meet these requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Jinko MCP server do?
The Jinko MCP server is the bridge that lets Claude use Jinko. It allows Claude to search flights and hotels, manage bookings, handle ancillaries and work with hosted checkout, following the permissions you set. Where Jinko offers a direct API instead, we can use that route as well.
Is connecting Claude to Jinko secure?
Security depends on how the connection is set up. We use the API key method with least-privilege access, store credentials securely and log every action. Consequential changes can require human approval. We cannot guarantee security outcomes, but we design the setup to limit risk.
What can Claude actually do in Jinko?
Typically, Claude can search flights and hotels, review trip details, create and modify bookings, add or manage ancillaries and start hosted checkout. The exact actions available depend on the access granted and on what Jinko exposes through its interface.
How long does setup take?
Timelines vary with the number of workflows and the systems involved. A focused single workflow often takes a few weeks from audit to launch, including testing and training. We confirm the timeline during the free automation audit.
Which Jinko plan or permissions do I need?
You need an account with Jinko that issues an API key with the access your workflow requires. The exact permissions depend on the functions you want Claude to use, so we confirm them with your Jinko account setup during the audit.