You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**MCP**|`plugins/jfrog/mcp.json`| Remote JFrog MCP server (OAuth, no API keys) |
10
-
|**Skills**|`plugins/jfrog/skills/`|11 AI skills covering Artifactory, Security, Access, CLI, Curation, Distribution, AppTrust, Runtime, Mission Control, Workers, and Patterns|
10
+
|**Skill**|`plugins/jfrog/skills/jfrog-platform/`| AI guidance for JFrog Platform operations|
11
11
|**Rule**|`plugins/jfrog/rules/jfrog-security.mdc`| Supply-chain security practices for dependency files |
12
12
|**Agent**|`plugins/jfrog/agents/supply-chain-security.md`| Dependency audit for CVEs, licenses, and curation |
13
13
14
14
## Prerequisites
15
15
16
-
1.**JFrog Platform** access (Cloud or self-hosted).
17
-
2. An admin enables the **JFrog MCP Server** on the platform (Cloud/SaaS only):
16
+
1.A **JFrog Cloud (SaaS)** subscription.
17
+
2. An admin enables the **JFrog MCP Server** on the platform:
18
18
-**Administration > General > Settings > MCP Server** → toggle ON.
19
19
3. Each developer configures Cursor with their JFrog Platform URL (see [Setup](#setup)).
20
-
4.**JFrog CLI** (`jf`) is used by several skills for authentication and REST API operations. It will be installed automatically if missing. Install manually via `brew install jfrog-cli` or the [official install script](https://jfrog.com/help/r/jfrog-cli/install-the-jfrog-cli).
21
20
22
21
## Setup
23
22
24
23
1. Install the plugin in Cursor.
25
24
2. Set the `JFROG_PLATFORM_URL` environment variable to your JFrog instance (e.g. `mycompany.jfrog.io`).
26
25
3. Restart Cursor. An OAuth window opens in your browser — authorize access.
27
26
28
-
No manual tokens or API keys are required. MCP workflows use OAuth; CLI/REST-based skills authenticate automatically via `jf config` browser login.
27
+
No tokens or API keys are required. Authentication is handled via OAuth.
2. An admin must **enable the JFrog MCP Server** on the platform:
9
9
- Navigate to **Administration > General > Settings** in the JFrog UI.
10
10
- Toggle the **MCP Server** option ON and save.
11
11
3. Set the `JFROG_PLATFORM_URL` environment variable to your JFrog instance (e.g., `mycompany.jfrog.io`).
12
-
4.**JFrog CLI** (`jf`) is used by several skills for authentication and REST API operations. It will be installed automatically if missing. Install manually via `brew install jfrog-cli` or the [official install script](https://jfrog.com/help/r/jfrog-cli/install-the-jfrog-cli).
13
12
14
-
Authentication is handled automatically — **OAuth**for MCP-based workflows, **browser-based login** (`jf config`) for CLI/REST-based skills. No manual API keys or tokens required.
13
+
Authentication is handled via **OAuth**— no API keys required.
15
14
16
15
## Included
17
16
18
-
| Component | Path | Description |
19
-
|---|---|---|
20
-
|**MCP**|`mcp.json`| Remote JFrog MCP server (OAuth, no API keys) |
21
-
|**Rule**|`rules/jfrog-security.mdc`| Supply-chain security practices for dependency files |
22
-
|**Agent**|`agents/supply-chain-security.md`| Dependency audit for CVEs, licenses, and curation |
0 commit comments