alignment for jfrog mcp to be like claude

Author: yanivt-jfrog

plugins/jfrog/README.md

@@ -8,25 +8,27 @@ JFrog Platform integration for Cursor — artifact management, security scanning
 2. An admin must **enable the JFrog MCP Server** on the platform (Cloud/SaaS only):
    - Navigate to **Administration > General > Settings** in the JFrog UI.
    - Toggle the **MCP Server** option ON and save.
-3. Set the `JFROG_PLATFORM_URL` environment variable to your JFrog instance (e.g., `mycompany.jfrog.io`).
-4. **JFrog CLI** (`jf`) is used by the skills for authentication and REST/GraphQL API operations. If missing, the agent will attempt to install it. You can also install manually via `brew install jfrog-cli` or the [official install script](https://jfrog.com/help/r/jfrog-cli/install-the-jfrog-cli).
+3. Set the `JFROG_URL` (full URL, e.g. `https://mycompany.jfrog.io`) and `JFROG_ACCESS_TOKEN` environment variables — the built-in `jfrog` MCP needs both at launch.
+4. **Node.js** (≥ 14) — with `npx` on your `PATH` (used to launch `@jfrog/agent-guard`).
+5. **JFrog CLI** (`jf`) is used by the skills for authentication and REST/GraphQL API operations. If missing, the agent will attempt to install it. You can also install manually via `brew install jfrog-cli` or the [official install script](https://jfrog.com/help/r/jfrog-cli/install-the-jfrog-cli).
 
-CLI authentication options: run `jf login` for browser-based setup, or set the `JFROG_ACCESS_TOKEN` environment variable. MCP-based workflows authenticate via **OAuth** and require no additional configuration.
+CLI authentication options: run `jf login` for browser-based setup, or set the same `JFROG_ACCESS_TOKEN` from step 3.
 
 ## Included
 
 | Component | Path | Description |
 |---|---|---|
-| **MCP** | `mcp.json` | Built-in JFrog MCP at `https://${JFROG_PLATFORM_URL}/mcp` (server name: `jfrog`). Always available, not subject to AI Catalog policy — see [JFrog MCP](#jfrog-mcp). |
+| **MCP** | `mcp.json` | Built-in JFrog MCP routed through `@jfrog/agent-guard` to `${JFROG_URL}/mcp` (server name: `jfrog`). Always available, not subject to AI Catalog policy — see [JFrog MCP](#jfrog-mcp). |
 | **Hook** | `hooks/hooks.json` | Agent Guard — MCP server governance via JFrog AI Catalog |
 
 ### JFrog MCP
 
-The plugin ships a built-in `jfrog` MCP registered in `mcp.json`, pointing
-at `https://${JFROG_PLATFORM_URL}/mcp`. Cursor launches it automatically
-when the plugin is enabled. If your Cursor admin enforces a URL allowlist,
-permit `https://${JFROG_PLATFORM_URL}/mcp` (or a wildcard like
-`https://*.jfrog.io/mcp`).
+The plugin ships a built-in `jfrog` MCP registered in `mcp.json`. Cursor
+launches it automatically as `npx @jfrog/agent-guard` with
+`_JF_ARGS=mcp=jfrog-mcp`. agent-guard recognizes that shape, skips the AI
+Catalog, and connects directly to `${JFROG_URL}/mcp` with
+`Authorization: Bearer ${JFROG_ACCESS_TOKEN}` (both env vars are listed
+under [Prerequisites](#prerequisites)).
 
 ### Skills
 

plugins/jfrog/templates/jfrog-mcp-management.md

@@ -1,27 +1,28 @@
 # Built-in `jfrog` MCP
 
-The plugin ships a built-in `jfrog` MCP at
-`https://${JFROG_PLATFORM_URL}/mcp` in its read-only `mcp.json`.
-**Hard rules** (apply before any MCP action below):
-
-- `jfrog` is always available with respect to AI Catalog policy;
-  never tell the user it's blocked or missing for catalog reasons.
-- NEVER run any Agent Guard flow (`--inspect`, `--login`, install,
-  remove) against `jfrog`, and NEVER edit or delete its entry.
-  Removal is only possible by uninstalling the plugin from Cursor.
+The plugin ships a built-in `jfrog` MCP in its read-only `mcp.json`,
+launched as `npx @jfrog/agent-guard` with `_JF_ARGS=mcp=jfrog-mcp`.
+agent-guard recognizes that shape, skips the AI Catalog, and connects
+directly to `${JFROG_URL}/mcp`. **Hard rules** (apply before any MCP
+action below):
+
+- `jfrog` is always available; never tell the user it's blocked,
+  missing, or pending because of catalog/entitlement.
+- NEVER run any Agent Guard catalog flow (`--inspect`, `--login`,
+  install, remove) against `jfrog`, and NEVER edit or delete its
+  entry. Removal is only possible by uninstalling the plugin from
+  Cursor.
 - In any "currently installed" listing, report `jfrog` as
   `scope: plugin (jfrog)`, `managed-by: plugin`. The rest of this
   document does not apply to it.
-- If the AI Catalog also publishes the JFrog MCP (typically as
-  `jfrog-mcp`) and the user wants catalog-managed tool policy,
-  install it via the standard catalog flow under a different
-  `mcpServers` key — e.g., `jfrog-catalog` — so it coexists with
-  the built-in `jfrog`. Tell the user about the rename and that
-  they end up with both entries.
-- Cursor's enterprise admin **MCP Configuration** panel sits above
-  plugins and CAN block `jfrog`. If the user reports `jfrog` is
-  missing, see "Built-in `jfrog` MCP missing under enterprise MCP
-  Configuration" in Troubleshooting.
+- Tool calls on the built-in `jfrog` are constrained by the JFrog
+  access token, not by AI Catalog tool policy. If the AI Catalog
+  also publishes the JFrog MCP (typically as `jfrog-mcp`) and the
+  user wants catalog-managed tool policy, install it via the
+  standard catalog flow (`_JF_ARGS=project=<key>&mcp=jfrog-mcp`)
+  under a different `mcpServers` key — e.g., `jfrog-catalog` — so
+  it coexists with the built-in `jfrog`. Tell the user about the
+  rename and that they end up with both entries.
 
 # MCP Server Management — JFrog Agent Guard
 
@@ -446,18 +447,16 @@ the display name.
   Tools & MCP** — never enabled. Re-run Step 4a
   (`cursor agent mcp enable <name>`); if the entry is brand-new,
   also `Developer: Reload Window` so Cursor picks up the file.
-- **Built-in `jfrog` MCP missing under enterprise MCP
-  Configuration** — the built-in `jfrog` server is HTTP at
-  `https://${JFROG_PLATFORM_URL}/mcp` and is filtered by Cursor's
-  admin **MCP Configuration** allowlist (Server/Command list with
-  Command or URL entries) like every MCP. Most common silent-block:
-  an allowlist with only Command entries (e.g. agent-guard-only
-  `npx ... @jfrog/agent-guard ...`) and zero URL entries — an HTTP
-  server has nothing to match. The plugin cannot bypass the admin
-  panel. Tell the user this is an enterprise-policy block (not a
-  plugin or AI Catalog issue) and to ask their Cursor admin to add a
-  URL entry covering `https://${JFROG_PLATFORM_URL}/mcp` in the
-  admin **MCP Configuration** panel.
+- **Built-in `jfrog` MCP missing** — almost always either (a)
+  `JFROG_URL` / `JFROG_ACCESS_TOKEN` unset (agent-guard fails fast at
+  startup; check the error in the Cursor MCP / Output panel), or (b)
+  Cursor's admin **MCP Configuration** allowlist filters the
+  `npx ... @jfrog/agent-guard` Command. The plugin cannot bypass the
+  admin panel — tell the user this is an environment / enterprise
+  policy issue (not a plugin or AI Catalog issue) and either to set
+  the env vars or to ask their Cursor admin to add a Command entry
+  covering `npx ... @jfrog/agent-guard` (no `--server` / `--mcp` /
+  `--project` args) in the admin **MCP Configuration** panel.
 - **Agent Guard: `multiple/no JFrog server configured`** (the agent guard
   cannot pick a JFrog server) — pass `--server <ID>` (after
   `jf c add <SERVER_ID>`) OR export both `JFROG_URL` and