Install Kong Skills
Install
/plugin marketplace add kong/ai-marketplace
/plugin install kong-konnect@ai-marketplace
/reload-pluginsWhat gets installed
- The
kong-konnectplugin package fromplugins/kong-konnect/ - The shared skills from
plugins/kong-konnect/skills/ - The
kong-konnectMCP server entry
Claude Code uses the plugin manifest in
plugins/kong-konnect/.claude-plugin/plugin.json
and the marketplace catalog in
.claude-plugin/marketplace.json.
Install components instead of the full plugin
Install all skills:
npx skills add kong/ai-marketplaceInstall only one skill:
npx skills add kong/ai-marketplace --skill gateway-plugin-datakitSkill-only installs do not require MCP authentication.
If you installed via gh skill, you can also update one installed skill with
gh skill update gateway-plugin-datakit.
Auto-update
Prefer Claude Code’s marketplace auto-update support over a custom shell hook.
In Claude Code:
- Run
/plugin. - Open the
Marketplacestab. - Select the
ai-marketplacemarketplace. - Enable or disable auto-update there.
If plugins were updated during a session, run /reload-plugins.
Be careful with auto-update. It can pull newer skill instructions automatically, which may introduce supply-chain or security risk if content changes upstream without review.
MCP authentication
The plugin loads the global URL from
plugins/kong-konnect/mcp.json and uses
OAuth. On first use Claude Code marks the server as needing authentication.
Run /mcp, select the kong-konnect server (shown as a plugin server when
installed via the plugin), and follow the browser login. From an interactive
terminal, the plugin CLI form is:
claude mcp login plugin:kong-konnect:kong-konnectThe command needs an interactive terminal. Without one it exits with
stdin isn't a terminal. claude mcp login kong-konnect applies only to the
direct-add path below; with the plugin installed it fails with
No MCP server named "kong-konnect".
Claude Code silently suppresses the plugin server when a user, project, or
local MCP entry points to the same URL under any name, because manual entries
take precedence over plugin servers. Remove the old entry with
claude mcp remove <name> -s <local|user|project>, using its actual name and
scope, so the plugin server can appear in /mcp. The plugin does not need to
be reinstalled.
For the MCP server alone, run this shell command instead of installing the plugin:
claude mcp add --transport http kong-konnect https://global.mcp.konghq.com/Kong recorded a successful OAuth test of this direct-add flow on 2026-09-18. That test does not establish an end-to-end test of the plugin install path. See Claude Code’s MCP documentation for authentication steps.
For CI or headless use, see the separate PAT/SPAT configuration. Before switching an existing installation, follow the migration steps.
Plugin install
The repository packages all Kong Konnect skills and the hosted MCP server for Codex and ChatGPT. This is a repo marketplace install; public directory approval and publication are separate and are not claimed here.
From a checkout containing the Codex package:
codex plugin marketplace add .
codex plugin marketplace list
codex plugin add kong-konnect@ai-marketplaceAfter this change is available on the public default branch, the remote form is:
codex plugin marketplace add Kong/ai-marketplaceThe CLI install command enables the plugin. Complete its MCP OAuth prompt
when connecting and start a new session. Alternatively, restart the ChatGPT
desktop app, open the Plugins Directory, choose
Kong AI Marketplace, and install Kong Konnect. Complete the OAuth
browser login when prompted, then start a new chat and check that the Kong
skills and kong-konnect MCP tools are available. Client availability varies;
see OpenAI’s package and marketplace guide.
The repository marketplace is
.agents/plugins/marketplace.json.
It points to the package containing
plugins/kong-konnect/.codex-plugin/plugin.json,
which loads the skill directory and
plugins/kong-konnect/.mcp.json.
This generated Codex companion has the same content as the shared
plugins/kong-konnect/mcp.json.
The MCP configuration uses https://global.mcp.konghq.com/ without headers or
tokens; the client manages OAuth and dynamic client registration.
MCP only
To connect the server without installing the plugin or its skills:
codex mcp add kong-konnect --url https://global.mcp.konghq.com/
codex mcp login kong-konnectUse either the plugin connection or the manual connection. Remove an existing
manual entry with codex mcp remove kong-konnect before using the plugin.
See migration and headless authentication for legacy entries and
separate PAT/SPAT configuration for CI. Never add credentials to the package.
Skills only
npx skills add kong/ai-marketplace --agent codexThis installs skills without MCP wiring or OAuth. See shared installers for preview, update, and single-skill options.
Local plugin install
For local verification, install the plugin package from Kong AI Marketplace under Cursor’s local plugin directory:
- Create
~/.cursor/plugins/local/kong-konnect/. - Copy the contents of
plugins/kong-konnect/into that path so Cursor sees.cursor-plugin/plugin.jsonat the plugin root. - Restart Cursor or run
Developer: Reload Window. - Confirm
kong-konnectappears under installed plugins.
Use a real copied directory for local testing. A symlinked local plugin directory does not load reliably, while a copied directory does.
Once Kong AI Marketplace is listed in a Cursor marketplace, the same package
shape can also be installed through Cursor’s plugin UI or /add-plugin. The
local path above remains the contributor smoke-test flow.
What gets installed
- The
kong-konnectplugin package fromplugins/kong-konnect/ - The shared skills from
plugins/kong-konnect/skills/ - The
kong-konnectMCP server entry fromplugins/kong-konnect/mcp.json
Cursor uses the plugin manifest in
plugins/kong-konnect/.cursor-plugin/plugin.json
and the marketplace catalog in
.cursor-plugin/marketplace.json.
Skills without the plugin wrapper
Install all skills:
npx skills add kong/ai-marketplaceInstall only one skill:
npx skills add kong/ai-marketplace --skill gateway-plugin-datakitSkill-only installs do not require MCP authentication.
If you installed via gh skill, you can also update one installed skill with
gh skill update gateway-plugin-datakit.
MCP authentication
Cursor loads the plugin’s
mcp.json, which uses the global URL
without a bearer header. Cursor documents OAuth for remote servers in
mcp.json; the plugin-bundled entry has
not been tested by Kong as of 2026-09-18. On first use, follow the connection
prompt and complete the browser login.
From a checkout of this repository, the local install steps above can be run as:
mkdir -p ~/.cursor/plugins/local/kong-konnect
cp -R plugins/kong-konnect/. ~/.cursor/plugins/local/kong-konnect/Restart Cursor or run Developer: Reload Window, then connect the server.
For MCP alone, copy the shipped MCP entry into your Cursor MCP settings
instead of installing the plugin.
For CI or headless use, see the separate PAT/SPAT configuration. Before switching an existing installation, follow the migration steps.
Kong AI Marketplace provides Kiro Powers for AWS.
Install
- Browse powers at https://kiro.dev/powers.
- Select a power and click Install.
- Kiro IDE opens and lets you confirm installation.
From GitHub
- Open the Powers panel and choose Add power from GitHub.
- Enter the following repository URL: https://github.com/kong/ai-marketplace
- Click Install.
Notes
- If a power includes MCP integrations, Kiro registers them in
~/.kiro/settings/mcp.jsonunder the Powers section. -
To install from GitHub:
gh skill install kong/ai-marketplaceCopied!Install one skill:
gh skill install kong/ai-marketplace gateway-plugin-datakitCopied!
MCP authentication
Tested with Kiro CLI 2.23.1 on 2026-09-23 using fresh browser OAuth with PKCE
and explicit oauthScopes, without a token. Search, schema discovery, reads,
and a disposable control-plane create/read/delete test passed on the CLI
surface. Token refresh and the Kiro IDE one-click install route were not tested.
Add this entry to ~/.kiro/settings/mcp.json, preserving any existing servers:
{
"mcpServers": {
"kong-konnect": {
"url": "https://global.mcp.konghq.com/",
"oauthScopes": [
"konnect:read",
"konnect:write",
"offline_access",
"openid"
]
}
}
}Explicit oauthScopes are required for this Kiro CLI setup: without them,
Kiro omits the scope parameter and Kong Identity rejects authorization with
“The scope of your request is missing”.
For CI or headless integrations, use a separate hand-written configuration with a PAT or SPAT bearer token. See the migration steps before replacing an old stdio or PAT-configured entry.
For tools without a first-class plugin or extension wrapper in Kong AI Marketplace, use the shared skills plus the MCP config.
Skills
npx skills and gh skill are both supported install paths for the shared
skills in Kong AI Marketplace.
npx skills
Install all skills:
npx skills add kong/ai-marketplaceInstall a single skill:
npx skills add kong/ai-marketplace --skill gateway-plugin-datakitUpdate all globally installed skills:
npx skills update -g -yUpdate one installed skill:
npx skills update -g -y gateway-plugin-datakit--skill applies to npx skills add. The update command takes skill names
positionally.
gh skill
gh skill is available in GitHub CLI v2.90.0+ and is currently in public
preview.
Preview a skill before installing it:
gh skill preview kong/ai-marketplace gateway-plugin-datakitgh skill install kong/ai-marketplaceTo install a single skill directly, use:
gh skill install kong/ai-marketplace gateway-plugin-datakitIf gh skill does not pick the right host automatically, pass --agent.
Pin an install to a reviewed tag or SHA when you need reproducibility:
gh skill install kong/ai-marketplace gateway-plugin-datakit --pin v1.0.0Update all installed skills:
gh skill update --allUpdate one installed skill:
gh skill update gateway-plugin-datakitThese skill-only installs do not require MCP authentication.
To validate GitHub-side publishability without publishing:
gh skill publish --dry-runAuto-update caution
Be careful with any automatic update path. It can pull newer skill instructions without review, which may introduce supply-chain or security risk if content changes upstream.
If you use auto-update, prefer updating one known skill first:
npx skills update -g -y gateway-plugin-datakitOr with GitHub CLI:
gh skill update gateway-plugin-datakitClaude Code has a native plugin update flow. See its install page for the current recommended approach.
Remote MCP with OAuth
Use plugins/kong-konnect/mcp.json as
the checked-in reference for the global URL and header-free OAuth configuration.
The client flows below follow client documentation; Kong has not recorded
end-to-end OAuth tests for them as of 2026-09-18.
Claude.ai and Claude Desktop
For individual plans in Claude.ai, go to Customize → Connectors, click
+, then Add custom connector. Enter kong-konnect as the name and
https://global.mcp.konghq.com/ as the URL. Free users are limited to one custom
connector.
For Team and Enterprise plans, an Owner must first add the connector through Organization settings → Connectors, using Add → Custom → Web. Members can then connect to it individually.
Connect the server and complete the browser login when first prompted. No PAT is needed. Claude Desktop shares the connector once it is added in Claude.ai. This installs the remote connector, not the repository’s skills. See Claude’s custom connector instructions.
Codex CLI
Add the server directly:
codex mcp add kong-konnect --url https://global.mcp.konghq.com/Complete the browser login when prompted during setup or first use. If login has not started, run:
codex mcp login kong-konnectCodex documents remote MCP OAuth and the login command. The Codex plugin was removed pending marketplace approval; these commands configure the MCP server directly and do not install a plugin.
CI and headless clients
For clients such as the Copilot cloud agent that need non-interactive auth, use the separate PAT/SPAT example. Before switching an existing installation, follow the migration steps.