Troubleshoot the JFrog Agent Plugin

Symptoms

• claude plugin install jfrog@claude-plugins-official fails
• Error mentions SSH/port 22 or GitHub connection issues
• Installation hangs or times out when attempting to reach GitHub

Root Cause

Your network blocks SSH (port 22) to GitHub. Claude Code currently has a open issue in which it tries HTTP and not HTTPs. The plugin normally uses SSH by default, but can fall back to HTTPS (port 443) using the solutions below.

Solution 1: Use HTTPS (Recommended)

Requirements: Claude Code v2.1.144 or later. Check your version with claude --version

Set an environment variable before installing:

export CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1
claude plugin install jfrog@claude-plugins-official

This forces the plugin download over HTTPS/443 instead of SSH/22.

Solution 2: Configure Git

If environment variables aren't practical in your setup:

git config --global url."https://github.com/".insteadOf [email protected]:
claude plugin install jfrog@claude-plugins-official

This globally configures Git to use HTTPS for all GitHub URLs instead of SSH.

The MCP server URL is built from JFROG_PLATFORM_URL. Confirm that the variable is set in the environment that launches Devin, that it contains the host only without https:// and without a trailing slash, and that you have completed devin mcp login jfrog.

Plugin MCP tools are available within a Devin session. They might not appear yet in the MCP settings interface.

If the plugin couldn't resolve your host, it writes https://<JFROG_PLATFORM_URL>/mcp instead of a real MCP URL. Set JFROG_PLATFORM_URL where the IDE can read it, or run jf config add, then restart the IDE so the plugin fills in the host. Alternatively, edit ~/.junie/mcp/mcp.json, 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. For more information, see Install JFrog Agent Plugin for JetBrains IDEs.

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. If ~/.junie/mcp/mcp.json isn't valid JSON, the plugin reports the problem rather than rewrite the file.

/jfrog-init doesn't sign you in to the MCP server. The first JFrog MCP request in Junie triggers a one-time browser OAuth prompt. If the jfrog server needs authorizing or reconnecting, go to Settings > Tools > Junie > MCP Settings, then reload the window.

A local folder import is referenced in place and is not copied into ~/.kiro/powers/installed/, so the activation tool fails. This is expected for a local folder import. Install from GitHub instead.

The IDE reads the global ~/.kiro/skills/ directory as well as the Power steering, so a global kiro-cli install alongside the IDE Power surfaces JFrog from both. Either install the CLI at workspace scope in projects you do not open in the IDE, or give the CLI its own profile using KIRO_HOME, for example KIRO_HOME=~/.kiro-cli, so that its skills never land in the ~/.kiro/ directory the IDE reads. A single-surface setup has no duplication.

The bundled .mcp.json ships with a <JFROG_PLATFORM_URL> placeholder that you must replace with your JFrog Platform host. Confirm that you edited the file at the path shown by codex plugin list, then run codex mcp login jfrog and restart Codex.

To enable debug logging for the JFrog Agent Plugin:

1. In your terminal, run:

export JFROG_DEBUG_LOGS=true

Logs are written to <project-root>/.opencode/event-log.txt.

If you see a "bundled skills not found" error (a toast in the TUI and/or an ERROR line in the log), the installed package is incomplete or corrupted. Reinstall @jfrog/opencode-jfrog-plugin and restart OpenCode.

If the JFrog MCP shows 401 or an SSE error in opencode mcp list (or the TUI), the /mcp endpoint rejected the token. Make sure JFROG_ACCESS_TOKEN is a JWT access token (jf atc), not a 64-character reference token, and that it was issued for the same platform as JFROG_URL (check with jf c show).

MCP connection status is surfaced by OpenCode itself. This plugin only registers the server. With JFROG_DEBUG_LOGS=true, a non-JWT token also produces a WARNING line in the event log.