Jinko MCP server (documented endpoint)

Travel

Discover, price, book, and manage flights and hotels through Jinko's shared trip model, available consistently across MCP, HTTP API, and CLI interfaces. This is Jinko's documented endpoint for developers — the same trip data and booking model whether Neotask calls it through MCP or a plain HTTP request.

• Discover, price, book, and manage flights and hotels through one shared trip model
• Consistent behavior across MCP, HTTP API, and CLI interfaces
• Built for programmatic booking, not just interactive search

What you can automate

Jinko MCP server (documented endpoint)

Discover, price, book, and manage flights and hotels through Jinko's shared trip model, available consistently across MCP, HTTP API, and CLI interfaces. Useful for developers building travel agents that need programmatic booking and trip management.

Real workflows

Build a travel agent with programmatic booking

A developer building a travel assistant needs to book and later modify a trip programmatically. Jinko's documented endpoint gives Neotask a shared trip model that behaves the same whether it's called through MCP, HTTP, or CLI.

Frequently asked questions

How is this different from the standard Jinko connection?

This is Jinko's documented endpoint, built specifically for developers who need the same trip model consistently across MCP, HTTP API, and CLI interfaces.

Can it manage a trip after booking, not just create it?

Yes — the shared trip model covers discovery, pricing, booking, and ongoing management of flights and hotels.