AX-1644 - add jfrog mcp and fix list available#28
Open
yanivt-jfrog wants to merge 3 commits into
Open
Conversation
This reverts commit 4115436.
Two changes that mirror the same fix shipped on claude-plugin main as PR #18: 1. plugins/jfrog/mcp.json: drop the trailing slash on the bundled --registry URL (.../coding-agents-npm/ -> .../coding-agents-npm). Cursor's MCP loader (and Claude Code's) dedupes server entries by (command, registry-URL); when the user already has an AI-Catalog-installed jfrog-mcp / chrome-devtools-mcp / etc. under the same npx + same registry URL, the bundled jfrog is silently skipped. The trailing-slash difference is enough to make the URL string distinct so dedup no longer collapses them. Functionally identical for npm, the agent-guard hook allowlist, and the agent guard itself. 2. plugins/jfrog/templates/jfrog-mcp-management.md: drop the top-of-document "# Built-in jfrog MCP" priming section. That section's "Hard rules" (especially "in any 'currently installed' listing, report jfrog as ...") was strong enough to make the LLM re-classify generic listing questions ("Which MCP servers can I use?") as "ambiguous / both" and run the currently-installed flow before the catalog --list-available query, dropping the catalog rows from the response. Distribute the rules as small per-subsection notes that only fire when the LLM is actually doing that operation: - ## Adding an MCP: bundled jfrog is never installed via catalog; coexist as jfrog-catalog if catalog tool policy wanted. - ## Removing an MCP: removal is by uninstalling the plugin from Cursor only; never delete the bundled mcp.json entry. - ## Listing MCPs routing table: add "what MCPs can I use" and "which MCP servers can I use" to the Available-to-install row so the failing question is mapped unambiguously. - ### Currently installed step 3: report bundled jfrog as scope: plugin (jfrog), package: jfrog-mcp (bundled). The AX-1644 troubleshooting bullet and admin MCP Configuration guidance are preserved exactly. Co-authored-by: Cursor <cursoragent@cursor.com>
Trim the AX-1644 "Built-in jfrog MCP missing" bullet to the env-vars-only shape that matches vscode-plugin and the env-vars arm of claude-plugin's bullet. Drop the second arm referring to Cursor's admin "MCP Configuration" allowlist: that allowlist is a UI-only mechanism, not analogous to Claude's MDM allowedMcpServers / deniedMcpServers (a managed-settings.json file). Mentioning it next to "this is an environment / enterprise policy issue" was conflating two unrelated mechanisms; the bullet now matches the other two plugins so support guidance stays in sync across Claude / Cursor / VS Code. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.