Install JFrog Agent Plugin for OpenAI Codex
Install the JFrog Agent Plugin for OpenAI Codex with bundled Skills and MCP.
The JFrog Agent Plugin for OpenAI Codex 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 plugin also registers the JFrog Platform remote MCP server alongside those skills.
What's Included
The plugin bundles:
- JFrog Skills: The skills ship with the plugin. They also include
/jfrog-init, a readiness check you run after installing. For more information about JFrog skills, see JFrog Skills. - JFrog Platform MCP: Declared by default in
.mcp.jsonathttps://<JFROG_PLATFORM_URL>/mcp. Once the host URL is resolved and OAuth sign-in is complete, JFrog Platform tools become available in Codex alongside skills. See JFrog MCP.
Prerequisites
- A JFrog Platform instance you can authenticate against.
- OpenAI Codex installed, with plugin support. The
codex pluginCLI commands must be available. JFROG_PLATFORM_URL: A placeholder in.mcp.jsonthat/jfrog-initreplaces automatically with the host from yourjf config.- Node.js (v18 or higher), with
npxon yourPATH. - For running the bundled skills at runtime, the following must be on your
PATH:jfJFrog CLI,jq, andcurl.- A configured JFrog CLI server, for example through
jf loginorjf config add. For more information, see Download and Install the JFrog CLI.
Install the JFrog Agent Plugin for OpenAI Codex
Codex installs plugins from a marketplace. The repository root is the marketplace root, so you add the JFrog marketplace and then install the plugin from it.
To install the JFrog Agent Plugin for OpenAI Codex:
-
Open your terminal.
-
Add the JFrog marketplace and install the plugin:
codex plugin marketplace add jfrog/codex-plugin codex plugin add jfrog@codex-plugin -
Restart Codex.
-
Run the readiness check in a Codex session:
/jfrog-initThe check verifies Node.js, the JFrog CLI, your
jfserver connection and credentials, thejfrogMCP 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. It also fills in your JFrog Platform host in the plugin.mcp.json, replacing the<JFROG_PLATFORM_URL>placeholder, so you don't have to edit the file by hand. -
Sign in to the JFrog Platform MCP server and complete the browser sign-in:
codex mcp login jfrog -
Restart Codex.
Note
/jfrog-initdoesn'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.
-
To confirm the installation, browse the installed plugins in the Codex terminal interface with the
/pluginscommand, then runcodex mcp listand confirm that thejfrogserver and its tools are available. -
(Optional) To set the host manually instead, find the plugin install path with
codex plugin list | grep jfrog@codex-pluginThen edit
<PATH>/.mcp.jsonand replace<JFROG_PLATFORM_URL>in theurlvalue with your full JFrog Platform host. For example,mycompany.jfrog.io, or your self-hosted or custom domain.
For installation and configuration issues, see Troubleshoot the JFrog Agent Plugin.
Frequently Asked Questions
This section provides answers to frequently asked questions.
FAQs
Q: How are bundled skills updated?
A: Skills are vendored at a pinned version inside the plugin package. Updating them is a build-time step and requires a new plugin release from JFrog. There are no runtime skill updates.
Q: Why do I get an authentication error after running /jfrog-init?
A: /jfrog-init configures and validates your jf CLI login, but it does not sign you in to the JFrog Platform MCP server. If Codex reports an authentication error talking to the jfrog MCP server, run codex mcp login jfrog, complete the browser sign-in, and restart Codex. If the error comes from the jf CLI or the skills instead, your stored credentials are likely missing or expired — reconnect with jf login (or jf config add) and re-run /jfrog-init.
Re-run /jfrog-init whenever you switch projects, machines, or JFrog servers.
Related Topics
Updated 4 days ago
