Connected JFrog

Connect Claude Code to the JFrog Platform for artifact management, build information, and repository operations through a direct MCP integration.

When to Use This MCP Server

Connect this server when you need to:

• Search and retrieve artifacts from JFrog Artifactory repositories while resolving dependencies or investigating build issues in Claude Code
• Access build information, deployment history, and artifact metadata to trace where specific versions originated and where they were deployed
• Manage repository configurations, permissions, and replication settings as part of your DevOps workflow directly from your development environment

Consider alternatives when:

• You only need to download artifacts, where direct Maven, npm, or Docker registry client commands are simpler for single-artifact retrieval
• Your artifact management is handled by GitHub Packages, AWS CodeArtifact, or another platform that is not part of the JFrog ecosystem

Quick Start

Configuration

Copy
name: connected-jfrog
type: mcp
category: devtools

Example Connection

Copy
claude mcp:connect connected-jfrog

Available Tools

search-artifacts:    Search for artifacts by name, property, or checksum across repositories
get-build-info:      Retrieve build information including dependencies and published modules
list-repositories:   List all repositories with their type, package type, and configuration
get-artifact-info:   Get detailed metadata, properties, and download statistics for an artifact
manage-permissions:  View and update permission targets for repositories and builds

Core Concepts

JFrog MCP Integration Overview

Aspect	Details
Transport	Remote MCP endpoint connecting directly to JFrog Platform URL
Authentication	JFrog Platform access token or API key for authenticated operations
Repository Types	Local, remote, virtual, and federated repositories across all package types
Package Support	Maven, npm, Docker, PyPI, NuGet, Go, Helm, and 30+ package formats
Build Integration	Build info from CI/CD systems with dependency and artifact tracking

JFrog Platform Architecture

Claude Code IDE
    |
    v
[MCP Client] --HTTPS--> [JFrog Platform MCP Endpoint]
                              |
                              v
                     [JFrog REST API]
                              |
                    +---------+---------+
                    |         |         |
                    v         v         v
              [Artifactory [Build    [Access
               Repos]      Info]     Control]
                    \         |         /
                     [JFrog Platform]
                   Artifacts | Builds | Security

Configuration

Parameter	Type	Default	Description
JFROG_PLATFORM_URL	string	required	JFrog Platform URL (e.g., https://mycompany.jfrog.io)
JFROG_ACCESS_TOKEN	string	required	JFrog access token for API authentication
default_repository	string	none	Default repository key to scope artifact search operations
include_remote	boolean	true	Include remote repository caches in artifact search results
max_results	integer	50	Maximum number of artifacts to return from search operations

Best Practices

1. Use AQL for Complex Searches - JFrog's Artifactory Query Language (AQL) provides powerful search capabilities beyond simple name matching. Use search-artifacts with AQL syntax for precise queries filtering by properties, dates, and statistics.

2. Track Build Provenance - Use get-build-info to verify the provenance of artifacts before deploying them. Build information links artifacts to their source code, build environment, and dependency tree for audit compliance.

3. Scope Searches to Specific Repositories - Set default_repository to focus searches on the relevant repository. Unscoped searches across all repositories return results from remote caches, virtual repos, and other irrelevant sources.

4. Use Access Tokens with Minimum Scope - Generate JFrog access tokens with only the permissions needed for your development workflow. Read-only tokens are sufficient for artifact browsing and build information retrieval.

5. Monitor Artifact Storage Usage - Periodically review repository statistics to identify large or unused artifacts that consume storage. Cleanup policies and retention rules keep your Artifactory instance efficient and costs manageable.

Common Issues

1. Platform URL Returns 404 - Ensure the JFROG_PLATFORM_URL includes the full base URL without trailing slashes or API path segments. The MCP server appends the correct API paths automatically.

2. Access Token Insufficient Permissions - JFrog access tokens can be scoped to specific repositories and operations. If an operation returns 403, verify the token's permission scope includes the target repository and operation type.

3. Search Returns Cached Remote Artifacts - Remote repository caches store copies of artifacts downloaded from external sources. Set include_remote to false if you only want to see artifacts published to your local repositories.