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.json at https://<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 plugin CLI commands must be available.
  • JFROG_PLATFORM_URL: A placeholder in .mcp.json that /jfrog-init replaces automatically with the host from your jf config.
  • Node.js (v18 or higher), with npx on your PATH.
  • For running the bundled skills at runtime, the following must be on your PATH:

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:

  1. Open your terminal.

  2. Add the JFrog marketplace and install the plugin:

    codex plugin marketplace add jfrog/codex-plugin
    codex plugin add jfrog@codex-plugin
  3. Restart Codex.

  4. Run the readiness check in a Codex session:

    /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. 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.

  5. Sign in to the JFrog Platform MCP server and complete the browser sign-in:

    codex mcp login jfrog
  6. Restart Codex.

📘

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.

  1. To confirm the installation, browse the installed plugins in the Codex terminal interface with the /plugins command, then run codex mcp list and confirm that the jfrog server and its tools are available.

  2. (Optional) To set the host manually instead, find the plugin install path with

    codex plugin list | grep jfrog@codex-plugin

    Then edit <PATH>/.mcp.json and replace <JFROG_PLATFORM_URL> in the url value 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.

plusFAQs
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


Did this page help you?