Can AI agents automate JFrog Artifactory?

JFrog Artifactory is automatable today through the JFrog Platform REST APIs. This record is Artifactory repositories, packages, and builds on SaaS or self-managed JPDs, not Docker Hub. JFrog documents REST and OpenAPI coverage across the platform and states Artifactory has REST APIs for nearly everything. Current REST credentials are scoped access tokens sent as Authorization Bearer, X-JFrog-Art-Api, or basic username plus token. API keys are end of life as of Artifactory 7.98 and are not a current auth method. The official jf CLI wraps Artifactory, Xray, and Distribution REST APIs on Windows, macOS, and Linux with non-interactive access-token config. JFrog documents a first-party remote MCP server that is generally available on SaaS for all subscription levels at https://<JPD>/mcp after a Platform Admin enables it; clients complete OAuth. Self-hosted MCP remains Beta. Curation and Catalog MCP tools need a Unified Security or Ultimate Security subscription. Official Java client and platform webhooks are documented. Computer-use viability is unassessed. API and CLI both score 8; API is the best path because JFrog presents REST as the complete control plane the CLI consumes. MCP scores 7 because SaaS is GA but admin-gated and edition-split.

Best path today: api · Overall automatability: 8/10