Install JFrog Agent Power for Kiro

The JFrog Agent Power for Kiro ships official JFrog Skills within the package and registers them at load time, so JFrog capabilities are available to your agent out-of-the-box. When your environment is configured, the Power also registers the JFrog Platform remote MCP server alongside those skills. Kiro calls an installable extension a Power rather than a Plugin.

Kiro has two surfaces, and JFrog supports both from the same skills: the IDE Power, for the Kiro IDE Powers panel, and the CLI, for kiro-cli, the terminal agent. Install the surface you use. A single-surface setup needs no further configuration.

• Install the JFrog Agent Power in the Kiro IDE
• Install JFrog for kiro-cli
• Uninstall JFrog for kiro-cli

What's Included

The Power bundles:

• JFrog Skills: The skills ship with the Power. Because a Kiro Power can't bundle a skills/ directory, the IDE Power delivers them as steering files that Kiro loads automatically, so the knowledge works immediately and offline with no download. Deep reference material is bundled as #jfrog-references and #jfrog-ai-catalog-skills-references. For more information about JFrog skills, see JFrog Skills.
• JFrog Platform MCP: When the environment is configured, the Power registers the JFrog Platform remote MCP server at https://<JFROG_PLATFORM_URL>/mcp, so JFrog Platform tools appear in Kiro alongside the skills. The connection uses OAuth. Kiro opens a browser sign-in on first use and caches the session, so there is no bearer token to generate or paste into a configuration file. For more information, see JFrog MCP.

Prerequisites

• A JFrog Platform instance you can authenticate against.
• Kiro installed for the IDE Power, or kiro-cli installed for the CLI surface.
• JFROG_PLATFORM_URL: Your JFrog Platform hostname. The JFrog Platform MCP server uses it automatically once connected.

  📘

  Note:

  If you run /jfrog-init(as described in step 7 below), JFROG_PLATFORM_URL is automatically configured.

• Node.js (v18 or higher) — with npx on your PATH.
• For running the bundled skills at runtime, the following must be on your PATH:
  • jf JFrog CLI 2.100.0 or later, jq, and curl.
  • A configured JFrog CLI server, for example through jf login or jf config add. Generate an access token at https://<your-platform>/ui/admin/configuration/security/access_tokens. Once the JFrog CLI is configured, it handles authentication for all jf subcommands automatically, and no environment variables or .env file are required. For more information, see Download and Install the JFrog CLI.

Install the JFrog Agent Power in the Kiro IDE

Install the Power from its GitHub repository. The JFrog steering ships with the Power and loads automatically, so nothing else is required to start using it.

To install the JFrog Agent Power in the Kiro IDE:

1. Open Kiro and click the Powers icon in the sidebar.

2. Click Add Custom Power, then click Import power from GitHub.

3. Enter the repository URL https://github.com/jfrog/jfrog-kiro-power.

4. Press Enter.

5. Verify your prerequisites:

   Bash

   npm run verify-install                 # macOS and Linux
   pwsh scripts/verify-install.ps1        # Windows

6. (Optional) If you plan to invoke skills using slash commands (for example, /SKILL or /jfrog-init), install the global skill manifests first by running:

   bash

   curl -fsSL https://raw.githubusercontent.com/jfrog/jfrog-kiro-power/main/scripts/bootstrap-cli.sh | bash

7. Then, open a new agent chat in Kiro and run the readiness check:

   1. Text

      /jfrog-init

      The readiness check automatically inspects and configures your environment:

      • Node.js: Verifies compatible runtime installation.
      • JFrog CLI: Checks jf CLI installation, active server connections, and credentials (configures new connections if needed).
      • MCP Entry: Verifies the jfrog MCP server entry and resolves the host URL.
      • Entitlements: Validates your project setup and JFrog AI Catalog entitlement.
        /jfrog-init fixes detected issues upon your approval or outputs the exact command(s) to resolve them manually.

        📘

        Note:

        /jfrog-init is not part of the base Power bundle. It becomes available once JFrog skills are installed globally as cross-agent skills in ~/.agents/skills/ via jf agent skills install or the bootstrap script above.

8. To confirm the installation, open a new agent chat in Kiro and ask a JFrog question, such as searching for artifacts in Artifactory or whether a package is safe to use.

9. (Optional) If a request needs a skill's runnable helper script, install the scripts from a checkout of the repository with npm run install-scripts, which installs to ~/.kiro/jfrog-scripts/. Add -- --workspace to scope the install to the current workspace instead.

For installation and configuration issues, see Troubleshoot the JFrog Agent Plugin.

Install JFrog for kiro-cli

kiro-cli, the terminal agent, is a separate runtime from the IDE. It doesn't read ~/.kiro/powers/, so it can't consume the IDE Power. Its mechanism is skills in ~/.kiro/skills/, which the default agent loads automatically, so JFrog composes into any session. The install is additive and never registers JFrog as your agent, so kiro-cli chat composes JFrog alongside whatever else you use.

To install JFrog for kiro-cli:

1. Open your terminal.

2. Install the skills:

   Bash

   curl -fsSL https://raw.githubusercontent.com/jfrog/jfrog-kiro-power/main/scripts/bootstrap-cli.sh | bash

   From a checkout of the repository, run npm run install-cli instead, or npm run install-cli -- --workspace to scope the install to the current workspace.

3. Start a chat. No --agent flag is needed:

   Bash

   kiro-cli chat

4. (Optional) To pin a specific version, set JFROG_KIRO_REF=<tag|branch>.

5. (Optional) For headless or CI runs, trust the shell tool with kiro-cli chat --no-interactive --trust-tools=execute_bash "…". The runtime ID execute_bash and the friendly alias shell name the same tool.

JFrog work runs through the jf CLI, never curl.

Uninstall JFrog for kiro-cli

You can remove the JFrog skills and MCP entry without affecting your other Kiro files. Every JFrog skill directory uses the jfrog prefix, so your own files are left untouched.

To uninstall JFrog for kiro-cli:

1. Run rm -rf ~/.kiro/skills/jfrog*, or rm -rf "$KIRO_HOME/skills/jfrog*" if you installed with a custom KIRO_HOME.

2. Remove the MCP entry separately with kiro-cli mcp remove --name jfrog --scope global, using --scope workspace if you installed with --workspace.

Frequently Asked Questions

This section provides answers to frequently asked questions.

Related Topics

• JFrog Agent Plugin
• Install JFrog Agent Plugin for Cursor
• Install JFrog Agent Plugin for Claude Code
• Install JFrog Agent Plugin for VS Code
• Install JFrog Agent Plugin for OpenCode
• Install JFrog Agent Plugin for Devin
• Install JFrog Agent Plugin for OpenAI Codex