How to connect Jinko to OpenClaw (paste one key, 13 tools)

The usual route to Jinko access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Jinko setup: install one ClawHub skill, connect Jinko in the browser, and OpenClaw can call real Jinko actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

Copy this prompt into OpenClaw, or open the Jinko skill on ClawHub.

Prompt for OpenClaw

Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Jinko" (hith3sh/jinko-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/jinko-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Setup

It takes three steps to connect OpenClaw to Jinko.

1
Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin
2
Connect Jinko
Paste your API key in the dashboard.
3
Use it from chat
Ask OpenClaw: "What can you do with Jinko?"

Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

openclaw plugins install clawhub:clawlink-plugin

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Jinko in the ClawLink dashboard — paste your Jinko API key once.

Verify the connection by asking OpenClaw:

Use Jinko to find destinations and walk me through the result in plain English.

Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Jinko is connected in the dashboard, that agent calls the same 13 Jinko tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Jinko MCP for OpenClaw

Looking for a Jinko MCP server for OpenClaw? ClawLink connects Jinko to OpenClaw and exposes 13 Jinko tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Jinko integration works the same way.

What the OpenClaw Jinko integration can do

13 Jinko tools are ready for OpenClaw once the account is connected.

All 13 Jinko tools for OpenClaw

Tool	What it does
Find destinations `jinko_find_destinations`	Discover destinations reachable from one or more origins using cached fare data, with optional
Get hotel details `jinko_get_hotel_details`	Get descriptive property, policy, facility, image, and room metadata for one hotel
Get trip `jinko_get_trip`	Read the canonical current state of a trip, including items, travelers, contact, quote and
Search flight calendar `jinko_search_flight_calendar`	Search cached priced itineraries for known origins and destinations across exact or flexible
Search flights `jinko_search_flights`	Get live flight offers either by searching a route or by re-pricing one cached discovery offer
Search hotels `jinko_search_hotels`	Search live hotel availability and priced room rates for dates, occupancy, and one location
Add trip item `jinko_add_trip_item`	Add one flight or hotel offer to an existing trip
Create hosted checkout `jinko_create_hosted_checkout`	Quote a complete trip and create a hosted checkout URL for a person to review and pay
Create trip `jinko_create_trip`	Create a new trip containing one flight or hotel offer
List trip ancillaries `jinko_list_trip_ancillaries`	Create or reuse a price quote and list purchasable baggage, seat, meal, and other ancillary
Replace trip travelers and contact `jinko_replace_trip_travelers_and_contact`	Replace an existing trip's complete traveler list and optionally its booking contact
Select ancillaries `jinko_select_ancillaries`	Replace the ancillary selections for one trip item using offer IDs from List Trip Ancillaries
Remove trip item `jinko_remove_trip_item`	Remove one flight or hotel item from an existing trip

Try it: find the Jinko tool you need

Browse the 13 Jinko tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Use Jinko to find destinations and walk me through the result in plain English.

Pull the relevant data from Jinko, summarize it in plain English, and point out anything that needs attention.

Search Jinko for what I need, summarize the results, and tell me the next best action.

ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Jinko working from chat.

	Manual	ClawLink
Credential handling	Collect, validate, store, and rotate the Jinko API key yourself, then make sure every tool call uses the right account.	Users complete the hosted ClawLink setup once and the connected Jinko account becomes available to the agent without you building credential management.
Ongoing maintenance	You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Jinko.	ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usability	You still need to expose the right Jinko actions to the runtime in a format your agent can reliably use.	13 tools for Jinko are already exposed through ClawLink, so the agent can read and act from chat immediately.

ClawLink vs. Composio

Composio also exposes Jinko to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Jinko in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Jinko key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Jinko skill but can't call the tools

The ClawHub skill teaches OpenClaw about Jinko, but the calls run through the ClawLink plugin and your connected account. Make sure Jinko is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Connection succeeds but no tools appear

Reconnect Jinko from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling Jinko tools

Jinko tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Jinko call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Jinko returns 403 or "permission denied" on one action while others work

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

API key setup works but results look incomplete

Double-check that the API key for Jinko has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Jinko integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Jinko: link your Jinko account once in the browser and OpenClaw can call the Jinko API through 13 ready-made tools — no custom code or token handling.

How do I add Jinko to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Jinko skill from ClawHub, then you click Connect in the dashboard to authorize Jinko. OpenClaw calls the tools from the next message — no config files, and the Jinko key you paste is stored server-side instead of in your environment.

How long does it take to connect Jinko to OpenClaw?

About two minutes. Sign in, click Connect next to Jinko in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Jinko up myself?

OpenClaw installed the Jinko skill but can't call the tools

How to connect Jinko to OpenClaw

Setup

Install the plugin

Connect Jinko

Use it from chat