Install JFrog Agent Plugin for JetBrains IDEs

Install and configure the JFrog Agent Plugin for JetBrains IDEs, including Agent Skills and the JFrog Platform MCP server.

The JFrog Agent Plugin for JetBrains IDEs, published on the JetBrains Marketplace as JFrog for Coding Agents, ships official JFrog Skills within the package and delivers them to Junie at IDE startup, so JFrog capabilities are available to your agent out-of-the-box. The plugin also registers the JFrog Platform remote MCP server alongside those skills. It supports every JetBrains IDE on 2025.2 or later that runs Junie, including IntelliJ IDEA, PyCharm, WebStorm, GoLand, RubyMine, CLion, PhpStorm, Rider, and DataGrip.

Unlike the plugins for other agents, this one needs no install command and no configuration file of your own. A startup activity writes the skills and the MCP server entry into your Junie home directory, so installing the plugin and restarting the IDE completes the setup.

The plugin targets Junie, the JetBrains native coding agent. The IntelliJ AI Assistant chat can also drive external agents such as Claude Agent, Codex, and Gemini CLI through the Agent Client Protocol. Those agents manage their own configuration and aren't covered by this plugin. To use JFrog tooling with one of them, install the JFrog plugin for that agent directly.

What's Included

The plugin bundles:

JFrog Skills: The plugin writes the skills to ~/.junie/skills/ on IDE startup and refreshes them whenever the plugin version changes. Each JFrog skill directory is replaced on refresh, so a skill removed upstream leaves no stale files behind, and skills in the folder that don't belong to JFrog are left untouched. The bundle includes jfrog-init, a readiness check you run after installing. For more information, see JFrog Skills.
JFrog Platform MCP: The plugin adds a jfrog remote MCP server entry to ~/.junie/mcp/mcp.json, so JFrog Platform tools appear in Junie alongside the skills. The entry is merged rather than overwritten, so the Junie idea entry and any other servers you configured are preserved, and an entry that already resolves to your host is never replaced with a placeholder. The first JFrog MCP request triggers a one-time browser OAuth sign-in, so no API key is required. For more information, see JFrog MCP.

Junie discovers both by convention, reading skills from .junie/skills/ and MCP servers from .junie/mcp/mcp.json.

The following skills ship with the plugin.

Skill	Description
`jfrog`	JFrog Platform operations through the JFrog CLI and the REST and GraphQL APIs, covering JFrog Artifactory repositories, builds, permissions, users, access tokens, projects, Release Bundles, security audits, CVE lookups, and JFrog Advanced Security exposure queries.
`jfrog-package-curation`	Check whether a package is safe, curated, or allowed, then download it through Artifactory. Covers npm, Maven, PyPI, Go, and others.
`jfrog-ai-catalog`	Discover, install, update, remove, and publish agent skills and plugins hosted in the JFrog AI Catalog.
`jfrog-mcp-management`	Install, list, and remove MCP servers, and browse the MCP servers approved for your project.
`jfrog-reference-architecture`	JFrog Platform topology, sizing, deployment, and high availability and disaster recovery guidance.
`jfrog-setup-package-managers`	Bind package managers such as npm, pip, Maven, Gradle, Go, Docker, and Helm to Artifactory through `jf setup`.
`jfrog-init`	The readiness check described in the install procedure.

Prerequisites

The JFrog Platform you can authenticate against.
A JetBrains IDE on version 2025.2 or later, with Junie installed. Junie availability and minimum versions differ across the JetBrains IDEs, so check that your IDE offers it.
JFROG_PLATFORM_URL: Your JFrog Platform host, for example mycompany.jfrog.io. The plugin uses it to fill in the JFrog MCP server URL. If the variable isn't set, the plugin falls back to your JFrog CLI configuration at ~/.jfrog/jfrog-cli.conf.v*, using the server marked as default, or the single configured server if there's only one. Set the variable where the IDE can read it, because an IDE launched from the desktop doesn't inherit the environment of your login shell.
Node.js 18 or later, with npx on your PATH.
For running the bundled skills at runtime, the following must be on your PATH:
- jf JFrog CLI, jq, and curl.
- A configured JFrog CLI server, for example through jf login or jf config add. For more information, see Download and Install the JFrog CLI.
Access to JFrog AI Catalog for skills that work with the catalog and MCP servers.

📘
Note
Skills that work with JFrog AI Catalog and with MCP servers require a JFrog AI Catalog entitlement on your subscription.

❗️
IMPORTANT
Junie can't find a command (for example, node / npx / jf "command not found"), OR an installed MCP fails to start
In these cases, Junie may not pick up configuration from ~/.zshrc / ~/.bashrc, so tools installed via nvm or Homebrew could be missing from its PATH. This is mainly a macOS issue.

To see which folders Junie has:

Run echo $PATH in a Junie chat (often just /usr/local/bin and the system dirs are found).

Symlink your tools into one of those (for example, with Homebrew):

sudo ln -sf /opt/homebrew/bin/{node,npm,npx,jf} /usr/local/bin/.

Restart the IDE.

The JFrog skills need node, npx, and jf on the PATH, so make sure at least those are symlinked. With a version manager like nvm, whose paths change per version, first give it a stable path (for example, nvm's NVM_SYMLINK_CURRENT) and symlink from that.

On Linux/Windows the IDE normally inherits your PATH; if a tool is still missing, add its folder to your OS user PATH (Linux: ~/.profile; Windows: Edit environment variables for your account) and restart the IDE.

Install the JFrog Agent Plugin for JetBrains IDEs

The plugin is published on the JetBrains Marketplace. On startup, it writes the JFrog skills and the JFrog MCP server entry into your global Junie home directory.

To install the JFrog Agent Plugin for JetBrains IDEs:

In your JetBrains IDE, go to Settings > Plugins > Marketplace.
Search for JFrog for Coding Agents, then click Install.

📘
Note
Search for the full name. The Marketplace also lists an older, unrelated JFrog plugin under the name JFrog.
Restart the IDE. The plugin deploys its assets when a project opens, so the skills and the MCP server entry are in place once the IDE has restarted.
Open the Junie panel, then run the readiness check by typing /jfrog-init or by asking Junie to run jfrog-init.

The check verifies Node.js, the JFrog CLI, your jf server connection and credentials, the jfrog MCP entry, your project, and your JFrog AI Catalog entitlement. It fixes what it can, asking for your approval first, and prints the exact command to run for anything it can't fix.

📘
Note
Junie loads the skill on that explicit request. Custom /name slash commands are a Junie CLI feature, not an IDE one, so /jfrog-init works here as a request to the agent rather than as a registered command.
If Junie asks where the skill's own directory is, answer ~/.junie/skills/jfrog-init. The readiness check needs its absolute path to run its detectors, and only Claude Code resolves that path automatically.
Complete the browser sign-in on your first JFrog MCP request in Junie.
To confirm the installation, go to Settings > Tools > Junie > MCP Settings and check that the jfrog server is listed, then ask Junie a JFrog question such as listing your Artifactory repositories. There's no interactive /mcp command in the IDE. Typing /mcp in the Junie chat is treated as plain text.
If the plugin wrote the placeholder MCP URL because it couldn't resolve your host, you must set the host. Set JFROG_PLATFORM_URL or run jf config add, then restart the IDE so the plugin fills in the host on the next startup. Alternatively, edit ~/.junie/mcp/mcp.json directly, replace <JFROG_PLATFORM_URL> with your JFrog Platform host, and restart the IDE. The plugin doesn't guess a host when more than one JFrog CLI server is configured and none is marked as default.
```
https://<JFROG_PLATFORM_URL>/mcp
```
Where:
- <JFROG_PLATFORM_URL>: Your JFrog Platform host
For example:
```
https://mycompany.jfrog.io/mcp
```

📘
Note
/jfrog-init doesn't sign you in to the MCP server, so run it in addition to the sign-in step, not instead of it. Run it again whenever you switch projects, machines, or JFrog servers, or if you hit unexpected authentication or CLI errors.

If the deploy fails, the plugin doesn't block IDE startup. It raises a JFrog setup incomplete notification instead. You can complete configuration under ~/.junie. For installation and configuration issues, see Troubleshoot the JFrog Agent Plugin.

Frequently Asked Questions

This section provides answers to frequently asked questions.

plusFAQs

Q: How do I verify the JFrog Agent Plugin is active in my JetBrains IDE?

A: After restarting the IDE, confirm that the JFrog skills are present in ~/.junie/skills/ and that a jfrog entry exists in ~/.junie/mcp/mcp.json. In the IDE, go to Settings > Tools > Junie > MCP Settings and confirm that the jfrog server is listed. Then ask Junie a JFrog question. In the Junie panel you can also run /skills to list the skills Junie has loaded. For more information, see Install the JFrog Agent Plugin for JetBrains IDEs.

Q: Which JetBrains IDEs does the plugin support?

A: The plugin declares a dependency on the JetBrains platform rather than on any one IDE, so it installs across the family on 2025.2 or later. The limiting factor is Junie, not the plugin: install it in a JetBrains IDE that runs Junie.

Q: Why does a skill keep asking me for my JFrog project key?

A: By design, the skills never guess a project. Set the JF_PROJECT environment variable to skip the prompt.

Q: Does the plugin work with the IntelliJ AI Assistant or with external agents such as Claude Agent, Codex, and Gemini CLI?

A: No. The plugin targets Junie. Agents driven through the Agent Client Protocol manage their own configuration. To use JFrog tooling with one of them, install the JFrog plugin for that agent directly.

Q: Will the plugin overwrite my existing Junie MCP configuration or my other skills?

A: No. The MCP entry is merged into ~/.junie/mcp/mcp.json, so your existing MCP servers are preserved.

Q: Does `/jfrog-init` sign me in to the JFrog Platform MCP server?

A: No. /jfrog-init checks that the jfrog MCP entry exists and resolves its host, and it handles the jf CLI login, which is a separate credential. The MCP sign-in happens through a one-time browser OAuth prompt on your first JFrog MCP request in Junie.

Q: How are bundled skills updated?

A: Skills are vendored at a pinned version inside the plugin. The plugin refreshes ~/.junie/skills/ when the plugin version changes, so updating them requires a new plugin release from JFrog. There are no runtime skill updates.

What's Included

Prerequisites

IMPORTANT

Install the JFrog Agent Plugin for JetBrains IDEs

Frequently Asked Questions

Q: How do I verify the JFrog Agent Plugin is active in my JetBrains IDE?

Q: Which JetBrains IDEs does the plugin support?

Q: Why does a skill keep asking me for my JFrog project key?

Q: Does the plugin work with the IntelliJ AI Assistant or with external agents such as Claude Agent, Codex, and Gemini CLI?

Q: Will the plugin overwrite my existing Junie MCP configuration or my other skills?

Q: Does /jfrog-init sign me in to the JFrog Platform MCP server?

Q: How are bundled skills updated?

Related Topics

Q: Does `/jfrog-init` sign me in to the JFrog Platform MCP server?