Install JFrog Agent Plugin for Devin

Install the JFrog Agent Plugin for Devin with bundled Skills and MCP.

The JFrog Agent Plugin for Devin 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. Devin exposes each one as /jfrog:<skill-name>, for example /jfrog:jfrog-package-safety-and-download. This includes /jfrog:jfrog-init, a readiness check you run after installing. For more information about JFrog skills, see JFrog Skills.
  • JFrog Platform MCP: When the environment is configured, the plugin registers the JFrog Platform remote MCP server at https://<JFROG_PLATFORM_URL>/mcp, so JFrog Platform tools appear in Devin alongside the skills. Authentication uses OAuth, so no access token is stored in the plugin. For more information, see JFrog MCP.

Prerequisites

  • A JFrog Platform instance you can authenticate against.
  • Devin CLI installed, with plugins enabled for your organization. The devin plugins install command must be permitted. Devin Local is part of Devin Desktop.
  • JFROG_PLATFORM_URL: Your JFrog Platform host, set in the environment that launches Devin CLI or Devin Local (part of Devin Desktop). Use the host only, without https:// and without a trailing slash. For example, mycompany.jfrog.io.
    📘

    Note:

    If you run /jfrog-init(as described 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:

Install the JFrog Agent Plugin for Devin

You install the plugin from its GitHub repository using the Devin CLI. While Devin has no plugin marketplace, plugins installed through the CLI are automatically accessible through the Devin desktop app through Devin Local.

To install the JFrog Agent Plugin for Devin:

  1. Open your terminal.

  2. Install the plugin:

    devin plugins install jfrog/devin-plugin -y
  3. Start a Devin session and run the readiness check:

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

  4. Sign in to the JFrog Platform MCP server:

    devin mcp login jfrog
  5. Complete the browser sign-in, then start a new Devin CLI or Devin Local (part of Devin Desktop) session.

  6. To confirm the installation, run devin plugins info jfrog. The output lists the bundled skills and an MCP server named jfrog.

  7. In a session, run /mcp and confirm that jfrog is listed as Connected.

📘

Note

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

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 Devin?

A: Run devin plugins info jfrog and confirm that the skills and the jfrog MCP server are listed. In a session, run /mcp and check that jfrog appears and is Connected. You can also invoke a skill directly with /jfrog:jfrog-init to confirm that Devin resolves it (Install the JFrog Agent Plugin for Devin).

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

A: No. /jfrog: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, but it never authenticates to the MCP server itself. You still need to run devin mcp login jfrog and complete the browser sign-in.

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.

Related Topics


Did this page help you?