@gojinko/plugin

Jinko agent plugins

The Jinko Travel plugin for Claude Code, Codex, Cursor and Vellum: search flights, hotels and car rentals, build a trip, book it and manage the booking, through the Jinko MCP server (https://mcp.builders.gojinko.com/mcp).

Every host gets the same skill content (jinko-travel, plus a short host-specific section), and each package connects to the Jinko MCP server in its host's own format.

How this repository works

• It is generated. The packages here are rendered from a private build. Don't edit them by hand: a later release overwrites them.
• Changes land only through release PRs titled Release v<x.y.z>, one per release. Each release updates the packages, the marketplace files and RELEASE.json, which records the version and the source commits it was built from.
• Open issues here. Bug reports and questions about the plugin are welcome as GitHub issues on this repository. Pull requests that edit plugins/ can't be merged as they are; describe the change in an issue instead.

Layout

Each release brings:

Before you install: set JINKO_API_KEY

Every host authenticates with a Jinko API key, a jnk_… key. Create one in the Jinko dashboard (dashboard.gojinko.com → Developers → API keys).

Claude Code, Codex and Vellum read it from the JINKO_API_KEY environment variable. Export it in the shell session you start the agent from, reading it from your secret manager rather than writing the key into a plaintext file such as a shell profile:

export JINKO_API_KEY="$(<your secret manager> read <jinko-api-key-item>)"

• Claude Code sends it as Authorization: Bearer ${JINKO_API_KEY}. If the variable is unset, Claude Code sends the literal text ${JINKO_API_KEY} and the server answers 401: set the variable before you start Claude Code.
• Codex reads it through bearer_token_env_var.
• Vellum reads it through the plugin's local MCP proxy.

Cursor is different: the plugin declares JINKO_API_KEY as a plugin variable, used in the Authorization header, not as a shell environment variable. See Cursor below.

Install

Claude Code

claude plugin marketplace add jinkoso/jinko-agent-plugins
claude plugin install jinko@jinko-agent-plugins

Or, inside a Claude Code session:

/plugin install jinko --marketplace jinkoso/jinko-agent-plugins

Codex

codex plugin marketplace add jinkoso/jinko-agent-plugins
codex plugin add jinko@jinko-agent-plugins

Or, in the Codex TUI, add the marketplace as above and pick jinko from /plugins.

Cursor

• Cursor Marketplace: install Jinko from the Cursor Marketplace once it is approved there.
• Teams and Enterprise: Dashboard → Plugins & MCPs → Team Marketplaces → Add Marketplace → Import from Repo, and paste https://github.com/jinkoso/jinko-agent-plugins. A team admin then sets the JINKO_API_KEY value in the dashboard under Plugins, at install time or later through Configure on the plugin.
• Individual, from this repository: copy plugins/cursor into ~/.cursor/plugins/local/jinko, then restart Cursor or run Developer: Reload Window. How a local install picks up the JINKO_API_KEY plugin variable is still being verified; this section will say how once it is confirmed.

Vellum

Vellum users keep installing the Jinko plugin from jinkoso/jinko-vellum-plugin until the Vellum platform integration ships. plugins/vellum here is built from the same source and will become the install path then.

npm

The Claude Code and Codex package is also published to npm as @gojinko/plugin, with the same version as the release here. Install the plugin through the marketplaces above.

License

MIT