Skip to main content
Connect the Jinko Builder MCP with OAuth in production or an API key in sandbox.

​
Endpoint

​
Sandbox

Use the sandbox endpoint to test with isolated data before going to production:
Sandbox MCP uses a sandbox API key, not OAuth. Production and sandbox keys are separate. See Sandbox keys to create the key and choose the correct endpoint.

​
API key mode

Production uses OAuth by default. If the client does not support OAuth, send the API key as an Authorization: Bearer jnk_t_your_key header. The MCP endpoint does not read X-API-Key. That header is for the REST API. See Which header to send.

​
Guide the model with Jinko Travel

The MCP server gives the model access to Jinko tools. The Jinko Travel skill is an optional complement that helps the model choose the right tool, follow the booking flow, and apply the right rules for payment and post-booking changes. The skill does not replace the MCP connection. Use both when your client supports skills or reusable instruction files.

​
Tool results

A Builder MCP tool result can contain two channels: The MCP host decides which channel the model sees. Your integration should always read structuredContent when it needs result data.
Do not parse content[].text as JSON. Its wording can change. Use structuredContent for stable result data.