Ax-1425-update vscode marketplace metadata readme by MatanEden1 · Pull Request #11 · jfrog/vscode-plugin

MatanEden1 · 2026-05-13T19:59:13Z

Name
Ax-1425-update vscode marketplace metadata readme
Description
update readme file

comments
please check the versions i added:

Claude Code CLI(≥ 1.0)
Node.js (≥ 18)
Frog CLI (≥ 2.x, optional)

Replace the placeholder README with full plugin documentation covering prerequisites, installation options, authentication, usage, and troubleshooting for the JFrog MCP Gateway integration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

YoniMelki · 2026-05-13T21:55:09Z

-# vscode-plugin
+# JFrog MCP Integration for VS Code
+
+JFrog integration for [Visual Studio Code](https://code.visualstudio.com/) and **GitHub Copilot Chat**: connect your Copilot agent to the [JFrog Agent Guard](https://jfrog.com) for policy-governed MCP access, with all MCP servers installed exclusively through the **JFrog MCP Gateway**.


I don't think that JFrog Agent Guard should point to jfrog,com. Maybe to a specific page there

There won't be MCP Gateway soon. We shouldn't write it

YoniMelki · 2026-05-13T22:05:50Z

+
+Before installing, make sure you have:
+
+- **JFrog Platform access** — An active account with the AI Catalog enabled.


I think that we should talk about entitlements here

you mean something like:

Your JFrog subscription must include the AI Catalog entitlement. Contact your JFrog account team if you're unsure whether it's enabled.

before "An active account with the AI Catalog enabled." ?

YoniMelki · 2026-05-14T08:04:34Z

+- **JFrog project** — At least one MCP server allowed for your project.
+- **JFrog host URL and access token** — Your JFrog platform URL and a valid access token.
+- **VS Code** — With the **GitHub Copilot Chat** extension installed and signed in.
+- **GitHub Copilot editor preview features enabled** — In your GitHub organization settings, navigate to **Settings → Copilot → Policies → Editor preview features** and set it to **Enabled**. Also set the environment variable `JF_MCP_GATEWAY_FORCE_ENABLE=true`.


Not sure we need the feature enabled

you right. it's a mistake

YoniMelki · 2026-05-14T08:05:09Z

+- **JFrog host URL and access token** — Your JFrog platform URL and a valid access token.
+- **VS Code** — With the **GitHub Copilot Chat** extension installed and signed in.
+- **GitHub Copilot editor preview features enabled** — In your GitHub organization settings, navigate to **Settings → Copilot → Policies → Editor preview features** and set it to **Enabled**. Also set the environment variable `JF_MCP_GATEWAY_FORCE_ENABLE=true`.
+- **Node.js** (≥ 18) — with `npx` on your `PATH` — required so the `mcp-gateway` can be fetched on demand.


Are we sure we need starting from version >= 18?

i was not sure about it, an i mention it on the pr.
According to the mcp-proxy readme, it requires - Node.js 14 or later.

YoniMelki · 2026-05-14T08:16:18Z

+
+### Option 1 — Magic link (recommended)
+
+From the [JFrog Platform → AI/ML → Registry → Your Project → MCP Servers](https://jfrog.com), click **Install MCP**, choose **VS Code** as your IDE, then click **Install via magic link**. Alternatively, open this link in any browser:


Nice, let's have a better UX and provide a screenshot

the ux now is WOW

YoniMelki · 2026-05-14T08:28:18Z

+### Option A — JFrog CLI (`jf config add`)
+
+If you already have the JFrog CLI installed and configured, the plugin uses your existing authentication. To configure it:
+
+1. Open your terminal.
+2. Run:
+   ```bash
+   jf config add
+   ```
+3. Follow the interactive prompts to enter your JFrog Platform URL and access token.
+4. Restart your IDE / terminal to apply the changes.


I think that this is relevant only if the user didn't do it in the past

YoniMelki · 2026-05-14T09:17:35Z

+| ----------------------- | ---------------------------------------------------------- |
+| `JFROG_PLATFORM_URL`    | Your JFrog platform URL, e.g. `https://mycompany.jfrog.io` |
+| `JFROG_ACCESS_TOKEN`    | Your JFrog access token                                    |
+| `JF_PROJECT`            | Your project key                                           |


This envar is not necessary for authentication

you are only talking about JF_PROJECT ?

YoniMelki · 2026-05-14T09:18:41Z

+**macOS / Linux (zsh or bash):**
+
+Add the variables to your shell profile so they load automatically every time a terminal (or VS Code) starts.
+
+1. Open your profile (`~/.zshrc` on macOS or `~/.bashrc` on Linux):
+   ```bash
+   nano ~/.zshrc
+   ```
+2. Add the following lines at the bottom of the file:
+   ```bash
+   export JFROG_PLATFORM_URL="<your-platform-url>"
+   export JF_PROJECT="<your-project-key>"
+   export JFROG_ACCESS_TOKEN="<your-access-token>"
+   ```
+3. Save and exit (`Ctrl+O`, `Enter`, then `Ctrl+X`).
+4. Apply the changes:
+   ```bash
+   source ~/.zshrc
+   ```
+
+**Windows (PowerShell):**
+
+Use `setx` to save the variables permanently to your user account settings.
+
+```powershell
+setx JFROG_PLATFORM_URL "<your-platform-url>"
+setx JF_PROJECT "<your-project-key>"
+setx JFROG_ACCESS_TOKEN "<your-access-token>"
+```


I wouldn't explain HOW to set the environment variables

YoniMelki · 2026-05-14T09:20:06Z

+
+### How secrets are handled
+
+When an MCP server requires sensitive configuration (marked as `isSecret` in the server's metadata), the agent cannot set the value directly. Instead, it returns a CLI command for you to copy and run in your terminal. Secrets such as API keys, tokens, and connection strings are never exposed in the agent chat history.


Suggested change

When an MCP server requires sensitive configuration (marked as `isSecret` in the server's metadata), the agent cannot set the value directly. Instead, it returns a CLI command for you to copy and run in your terminal. Secrets such as API keys, tokens, and connection strings are never exposed in the agent chat history.

When an MCP server requires a sensitive configuration, the agent cannot set the value directly. Instead, it returns a CLI command for you to copy and run in your terminal. Secrets such as API keys, tokens, and connection strings are never exposed in the agent chat history.

Reflow the intro into three tight lines using <br> breaks and wrap the Option 3 settings.json snippet in braces so it parses standalone. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…nstructions and troubleshooting details

…n correction

MatanEden1 and others added 2 commits May 13, 2026 15:42

Update README.md with MCP integration documentation

bfaa584

MatanEden1 changed the title ~~Ax 1425 update vscode marketplace metadata readme~~ Ax-1425-update vscode marketplace metadata readme May 13, 2026

MatanEden1 assigned MatanEden1 and yanivt-jfrog and unassigned MatanEden1 May 13, 2026

YoniMelki requested changes May 14, 2026

View reviewed changes

MatanEden1 and others added 5 commits May 14, 2026 14:01

[AX-1425][vscode-plugin] Polish README intro and settings.json snippet

ed74bad

Reflow the intro into three tight lines using <br> breaks and wrap the Option 3 settings.json snippet in braces so it parses standalone. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

[AX-1425][vscode-plugin] Update README with MCP server installation i…

c78529e

…nstructions and troubleshooting details

Update README with environment variable setup and security notes

9c7e89a

Update README with JFrog subscription requirements and Node.js versio…

4059a51

…n correction

add pictures to show the flow

44379b5


		Before installing, make sure you have:

		- JFrog Platform access — An active account with the AI Catalog enabled.


		### Option 1 — Magic link (recommended)

		From the [JFrog Platform → AI/ML → Registry → Your Project → MCP Servers](https://jfrog.com), click Install MCP, choose VS Code as your IDE, then click Install via magic link. Alternatively, open this link in any browser:


		### How secrets are handled

		When an MCP server requires sensitive configuration (marked as `isSecret` in the server's metadata), the agent cannot set the value directly. Instead, it returns a CLI command for you to copy and run in your terminal. Secrets such as API keys, tokens, and connection strings are never exposed in the agent chat history.

	When an MCP server requires sensitive configuration (marked as `isSecret` in the server's metadata), the agent cannot set the value directly. Instead, it returns a CLI command for you to copy and run in your terminal. Secrets such as API keys, tokens, and connection strings are never exposed in the agent chat history.
	When an MCP server requires a sensitive configuration, the agent cannot set the value directly. Instead, it returns a CLI command for you to copy and run in your terminal. Secrets such as API keys, tokens, and connection strings are never exposed in the agent chat history.

Conversation

MatanEden1 commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

MatanEden1 commented May 13, 2026 •

edited

Loading