Artifact Registry MCP Server
Integrates with JFrog Artifactory to manage registry sessions, list repositories, search binaries, resolve Docker image tags and digests, verify SHA256 checksum integrity, and perform confirmation-gated binary uploads, release promotions, and stale snapshot cleanup.
Integrates with Sonatype Nexus Repository 3 to manage registry sessions, list repositories, search binaries, resolve Docker image tags and digests, verify SHA256 checksum integrity, and perform confirmation-gated binary uploads, release promotions, and stale snapshot cleanup.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Artifact Registry MCP Server upload build/libs/app-1.2.0.jar to Nexus dev and verify its checksum"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Artifact Registry MCP Server
Open-source Model Context Protocol (MCP) server owned by Pawan Gunjkar (pawangunjkar@gmail.com · GitHub). MIT licensed.
Production-grade MCP server supporting both Sonatype Nexus Repository 3 and JFrog Artifactory. Bridges CI/CD build pipelines (github-mcp and jenkins-mcp) and Kubernetes/OpenShift deployment automation (k8s-mcp).
Project Information
Item | Value |
Package |
|
CLI Entrypoint |
|
Runtime | Python 3.10+, FastMCP, stdio, httpx, pydantic |
Supported Registries | Sonatype Nexus Repository 3, JFrog Artifactory |
Supported Formats |
|
Security Model | Multi-session credential caching, Confirmation-gated mutations |
Sibling MCPs |
Related MCP server: JFrog Artifactory MCP Server
Architecture & Supply Chain Flow
flowchart TB
subgraph CI["Layer 1 — CI & Source Control"]
GH["github-mcp Actions"]
JK["jenkins-mcp Build Jobs"]
end
subgraph MCP["Layer 2 — Binary Supply Chain Control Plane"]
REG["artifact-registry-mcp"]
CS["CredentialStore (~/.artifact-mcp-cache)"]
GATE["Confirmation Gate (confirm=true)"]
end
subgraph BACKENDS["Layer 3 — Enterprise Registries"]
NEXUS["Sonatype Nexus Repository 3 (:8081)"]
JFROG["JFrog Artifactory (:8082)"]
end
subgraph DEPLOY["Layer 4 — Deployment Runtime"]
K8S["k8s-mcp (OpenShift / EKS / AKS / GKE)"]
end
GH -->|"artifact_upload_binary"| REG
JK -->|"artifact_upload_binary"| REG
REG --> CS
REG --> GATE
GATE -->|"Upload / Promote / Prune"| NEXUS
GATE -->|"Upload / Promote / Prune"| JFROG
NEXUS -->|"artifact_verify_checksum_integrity"| REG
JFROG -->|"artifact_verify_checksum_integrity"| REG
REG -->|"artifact_get_docker_image_tags_and_digests"| K8SsequenceDiagram
autonumber
actor Agent as AI Coding Agent
participant CI as CI (jenkins-mcp / github-mcp)
participant MCP as artifact-registry-mcp
participant Reg as Nexus 3 / Artifactory
participant K8s as k8s-mcp
Agent->>CI: Run build & tests (output jar/archive + SHA256)
CI-->>Agent: Build artifact + Expected SHA256
Agent->>MCP: artifact_upload_binary(confirm=true)
MCP->>Reg: Upload binary & compute remote SHA256
Reg-->>MCP: Remote checksum attestation
Agent->>MCP: artifact_verify_checksum_integrity(...)
MCP-->>Agent: ATTESTATION PASSED (Tamper-Free)
Agent->>MCP: artifact_promote_release(dev-local -> prod-release)
MCP->>Reg: Atomic copy / staging promotion
Agent->>MCP: artifact_get_docker_image_tags_and_digests(...)
MCP-->>Agent: Resolved immutable sha256:... digest
Agent->>K8s: k8s_update_deployment_image(image@sha256:...)12 Core Tools Reference
Connection & Session Management (5 Tools)
Tool | Access | Description |
| Read-only | Connect to Sonatype Nexus 3 or JFrog Artifactory and create a named session |
| Read-only | Check connection health, version, authenticated user, and storage quota |
| Read-only | Disconnect an active session and close HTTP connections |
| Read-only | List all active and cached registry sessions with masked credentials |
| Read-only | Save connection credentials to local cache file |
Binary Discovery & Supply-Chain Attestation (4 Tools)
Tool | Access | Description |
| Read-only | List repositories filtered by format ( |
| Read-only | Search components by name, group, version, or SHA256; returns URLs, timestamps, checksums |
| Read-only | Resolves immutable |
| Read-only | Compares expected SHA256 from CI against stored checksum before allowing deployment |
Confirmation-Gated Mutating Tools (3 Tools)
Tool | Access | Description |
| Confirm ( | Computes local SHA256, uploads file to registry, and verifies remote checksum match |
| Confirm ( | Promotes immutable artifact from staging to release repository without rebuilding |
| Confirm ( | Prunes stale snapshot builds beyond retention count ( |
Setup & Configuration
Environment Variables
Configure the following environment variables (or let the agent prompt you via artifact_connect):
# Registry Type: "nexus" or "artifactory"
export ARTIFACT_REGISTRY_TYPE=nexus
# Registry Base URL
export ARTIFACT_REGISTRY_URL=http://localhost:8081
# Credentials
export ARTIFACT_REGISTRY_USER=admin
export ARTIFACT_REGISTRY_TOKEN=your-token-or-passwordCursor Setup (.cursor/mcp.json)
{
"mcpServers": {
"artifact-registry": {
"command": "uvx",
"args": ["artifact-registry-mcp"],
"env": {
"ARTIFACT_REGISTRY_TYPE": "${ARTIFACT_REGISTRY_TYPE}",
"ARTIFACT_REGISTRY_URL": "${ARTIFACT_REGISTRY_URL}",
"ARTIFACT_REGISTRY_USER": "${ARTIFACT_REGISTRY_USER}",
"ARTIFACT_REGISTRY_TOKEN": "${ARTIFACT_REGISTRY_TOKEN}"
}
}
}
}Claude Code Setup (.mcp.json)
{
"mcpServers": {
"artifact-registry": {
"command": "uvx",
"args": ["artifact-registry-mcp"],
"env": {
"ARTIFACT_REGISTRY_TYPE": "${ARTIFACT_REGISTRY_TYPE}",
"ARTIFACT_REGISTRY_URL": "${ARTIFACT_REGISTRY_URL}",
"ARTIFACT_REGISTRY_USER": "${ARTIFACT_REGISTRY_USER}",
"ARTIFACT_REGISTRY_TOKEN": "${ARTIFACT_REGISTRY_TOKEN}"
}
}
}
}Testing & Quality Assurance
Run the test suite:
uv run -m unittest discover testsBuild the Agensi skill package:
uv run python scripts/build_agensi_zip.pyBuild distribution packages (wheel and sdist):
uv buildLicense
MIT License. Copyright (c) 2026 Pawan Gunjkar.
Available Tools
12 toolsartifact_cleanup_old_snapshotsA
Identify and prune stale snapshot artifacts to reclaim storage.
⚠️ CONFIRMATION-GATED MUTATING TOOL: Requires dry_run=false AND confirm=true to delete.
Finds all snapshot versions of a component, sorts by timestamp/version descending, preserves the latest keep_latest_n snapshots, and simulates or deletes stale items.
Purpose: Maintain storage quotas and enforce artifact retention policies. When to Use: In Workflow 4 during scheduled maintenance or when storage alerts trigger. Behavior: Dry-run simulation by default. Destructive deletion when dry_run=false and confirm=true. Side Effects: Permanently deletes pruned snapshot artifacts when executed.
Args: repository: Repository containing snapshot artifacts (e.g. 'maven-snapshots', 'libs-snapshot-local') component_name: Name of the component to clean up (e.g. 'billing-engine') keep_latest_n: Number of most recent snapshots to preserve (default: 5) dry_run: If True, simulates cleanup without deleting files (default: True) confirm: Must be True when dry_run=False to execute permanent deletion (default: False) session_name: Session to use (default: 'default')
Inputs: repository (required), component_name (required), confirm, dry_run, +2 more. Returns: result
artifact_connectA
Connect to Sonatype Nexus 3 or JFrog Artifactory and create a named session.
Probes registry system status and version to verify connectivity and credentials. Credentials are automatically cached to ~/.artifact-mcp-cache/credentials.json.
Purpose: Establish an authenticated session before calling any registry tool. When to Use: At the start of an artifact supply chain workflow or to switch between staging/production registries using named sessions. Behavior: Read-Only probe (no artifacts mutated). Side Effects: Caches session credentials locally.
Args: registry_type: 'nexus' (Sonatype Nexus 3) or 'artifactory' (JFrog Artifactory) base_url: Registry base URL (e.g. 'http://localhost:8081' or 'https://myorg.jfrog.io/artifactory') token_or_password: Password, API Token, or Access Token username: Username (e.g. 'admin' or 'ci-agent') session_name: Name for this session, e.g. 'prod', 'staging' (default: 'default')
Inputs: base_url, username, session_name, registry_type, +1 more. Returns: result
artifact_disconnectA
Disconnect an active artifact registry session and close HTTP connections.
Purpose: Clean up open network sessions and release memory. When to Use: When switching environments or finishing a pipeline run. Behavior: Closes local HTTP client. Side Effects: Removes session from active memory.
Args: session_name: Session to disconnect (default: 'default')
Inputs: session_name. Returns: result
artifact_get_docker_image_tags_and_digestsA
Query Docker/OCI repositories to resolve an immutable sha256:... image digest.
Queries Docker v2 manifest endpoints and AQL in Nexus and Artifactory. Produces an immutable image reference (image@sha256:...) and ready-to-run tool arguments for k8s-mcp rollouts.
Purpose: Bridge container registry images to Kubernetes deployments securely. When to Use: Right before calling k8s-mcp to deploy or update a container workload. Behavior: Read-Only query. Side Effects: None.
Args: repository: Docker repository key/name in the registry (e.g. 'docker-local' or 'docker-hosted') image_name: Container image name (e.g. 'payment-service' or 'microservices/auth') limit: Maximum number of tags to return (default: 20) session_name: Session to query (default: 'default')
Inputs: image_name (required), repository (required), limit, session_name. Returns: result
artifact_list_repositoriesA
List repositories filtered by package format and repository type.
Works across both Nexus 3 (/service/rest/v1/repositories) and Artifactory (/api/repositories).
Purpose: Inspect repository topology and locate target repos for upload or promotion. When to Use: During supply chain discovery before publishing or pulling artifacts. Behavior: Read-Only query. Side Effects: None.
Args: format_filter: Filter by package format: 'maven2', 'docker', 'npm', 'pypi', 'helm', 'raw' (or 'generic') type_filter: Filter by type: 'hosted' (or 'local'), 'proxy' (or 'remote'), 'group' (or 'virtual') session_name: Session to query (default: 'default')
Inputs: type_filter, session_name, format_filter. Returns: result
artifact_list_sessionsA
List all active and cached registry sessions with masked credentials.
Purpose: Review available registry targets, environments, and versions. When to Use: To determine which sessions are configured before executing workflows. Behavior: Read-Only local inspection. Side Effects: None.
Inputs: no named parameters. Returns: result
artifact_promote_releaseA
Promote an immutable artifact from staging/snapshot to production release repository.
⚠️ CONFIRMATION-GATED MUTATING TOOL: Requires confirm=true to execute.
Promotes a tested, immutable component from staging (e.g. 'dev-local', 'maven-staging') to production release (e.g. 'prod-release', 'maven-releases') without rebuilding, maintaining complete provenance and cryptographic integrity.
Purpose: Supply-chain promotion between pipeline stages. When to Use: In Workflow 2 after integration/smoke tests pass. Behavior: MUTATING. Copies component to target release repository. Side Effects: Modifies target release repository contents.
Args: source_repo: Source repository key (e.g. 'dev-local', 'staging-repo') target_repo: Target release repository key (e.g. 'prod-release', 'maven-releases') artifact_or_build_name: Name of the artifact or build component (e.g. 'cart-service') version: Version string to promote (e.g. '1.5.0') confirm: Must be True to execute promotion (default: False) session_name: Session to use (default: 'default')
Inputs: version (required), source_repo (required), target_repo (required), artifact_or_build_name (required), +2 more. Returns: result
artifact_save_credentialsA
Save registry credentials to the local persistent cache file.
Purpose: Cache connection details so future sessions can reconnect automatically. When to Use: When pre-configuring staging/production environments without running queries. Behavior: Local file write to ~/.artifact-mcp-cache/credentials.json. Side Effects: Overwrites existing cached credentials for session_name.
Args: registry_type: 'nexus' or 'artifactory' base_url: Registry base URL token_or_password: Password, API Token, or Access Token username: Username (e.g. 'admin') session_name: Session name to store (default: 'default')
Inputs: base_url (required), registry_type (required), token_or_password (required), username, +1 more. Returns: result
artifact_search_binariesA
Search components and artifacts across Nexus or Artifactory.
Returns download URLs, exact versions, creation/modification timestamps, and SHA256/SHA1/MD5 checksums.
Purpose: Locate specific binaries or verify build component presence. When to Use: To locate release artifacts before deployment or check artifact metadata. Behavior: Read-Only search. Side Effects: None.
Args: name: Artifact or component name (supports wildcards/substrings, e.g. 'order-service') group_or_repo: Repository name or Maven groupId (e.g. 'libs-release-local' or 'com.myorg') version: Specific version string (e.g. '1.4.2' or '2.0.0-SNAPSHOT') sha256: Exact 64-character SHA256 checksum to look up session_name: Session to query (default: 'default')
Inputs: name (required), sha256, version, session_name, +1 more. Returns: result
artifact_statusA
Check connection health, authenticated user, registry version, and storage quota.
Probes status endpoints (Nexus /service/rest/v1/status, Artifactory /api/system/ping), retrieves server version, and summarizes repository storage metrics.
Purpose: Verify registry availability, user privileges, and storage capacity. When to Use: Before initiating large binary uploads or checking health. Behavior: Read-Only probe. Side Effects: None.
Args: session_name: Artifact registry session to inspect (default: 'default')
Inputs: session_name. Returns: result
artifact_upload_binaryA
Upload a local build artifact/archive to Nexus or Artifactory with checksum verification.
⚠️ CONFIRMATION-GATED MUTATING TOOL: Requires confirm=true to execute.
Computes local SHA256/SHA1/MD5 checksums, uploads the binary to the destination repository, and immediately verifies the remote checksum match.
Purpose: Publish build archives, JARs, wheels, or tarballs to the registry. When to Use: In Workflow 1 after jenkins-mcp or github-mcp build completes. Behavior: MUTATING. Writes binary to registry storage. Side Effects: Consumes registry storage space.
Args: repository: Destination repository (e.g. 'maven-releases', 'libs-snapshot-local') local_file_path: Absolute or relative path to the local file to upload target_path: Destination path in the repository (e.g. 'com/corp/auth/1.0.0/auth-1.0.0.jar') maven_coords: Optional dict of Maven coordinates {'groupId': '...', 'artifactId': '...', 'version': '...', 'packaging': 'jar'} confirm: Must be True to execute upload (default: False) session_name: Session to use (default: 'default')
Inputs: repository (required), target_path (required), local_file_path (required), confirm, +2 more. Returns: result
artifact_verify_checksum_integrityA
Compare the SHA256 digest generated by CI against registry checksum before deployment.
Verifies cryptographic attestation: compares the expected SHA256 (produced by github-mcp GitHub Actions or jenkins-mcp build jobs) against the checksum stored in Nexus or Artifactory. Blocks deployment if tampering or corruption is detected.
Purpose: Supply-chain security attestation gate. When to Use: In CI/CD pipelines right before deployment to Kubernetes/OpenShift. Behavior: Read-Only verification. Side Effects: None.
Args: artifact_path_or_url: Remote artifact path (e.g. 'libs-release-local/com/corp/app-1.0.jar') or full URL expected_sha256: 64-character SHA256 digest from CI build or SBOM session_name: Session to query (default: 'default')
Inputs: expected_sha256 (required), artifact_path_or_url (required), session_name. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Most tools target clearly distinct registry actions and resources, with confirmation-gated mutations separated from read-only operations. The main overlap is between artifact_save_credentials and artifact_connect, since connect also caches credentials, but descriptions clarify the difference.
All tools use a consistent artifact_ prefix with snake_case naming, mostly following an artifact_verb_noun pattern. artifact_status is the minor exception, acting as a noun-only name rather than artifact_get_status.
The 12-tool set is well-scoped for an artifact registry server, covering session management, discovery, verification, upload, promotion, and cleanup. Each tool appears to earn its place without excessive surface area.
The surface covers the core artifact supply-chain lifecycle well: connect, inspect, search, verify, upload, promote, and clean up. Minor gaps include no direct artifact download tool and no general-purpose artifact deletion beyond snapshot cleanup.
Related MCP Connectors
Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI.
Search, read and save your team's AI-generated work in Artifactry: code, documents and diagrams.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Maven artifacts in JFrog Artifactory by reusing credentials from ~/.m2/settings.xml and providing tools like getting latest stable versions, listing artifacts, and checking dependency updates.-
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that provides seamless integration with JFrog Artifactory, enabling AI assistants to manage artifacts, repositories, and perform cleanup operations through natural language interactions.-

JFrog Remote MCP Serverofficial
FlicenseNot gradedqualityCmaintenanceConnects AI coding assistants to the JFrog platform, enabling natural-language queries for resource management, artifact discovery, security monitoring, and catalog curation.15-- AlicenseNot gradedqualityBmaintenanceEnables autonomous AI agents and CI/CD runners to discover repository modules, scan outdated dependencies, fetch version histories, and apply verified dependency updates with major-version safety guardrails across polyglot monorepos.105 npmMIT