Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Harness Artifact Registry (BYOK) — connector documentation

  • MCP endpoint: https://byok-harness-artifacts.connectorbay.com/mcp
  • REST API: POST https://byok-harness-artifacts.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-harness-artifacts.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Harness Artifact Registry Harness personal access token or service account token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-harness-artifacts.connectorbay.com/health · Tool schemas: https://byok-harness-artifacts.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-harness-artifacts · agent@connectorbay.com

What Harness Artifact Registry (BYOK) is for

Harness Artifact Registry (BYOK) lets an AI assistant read your own Harness Artifact Registry data through the Harness Artifact Registry API with a key you supply (Harness personal access token or service account token). Read-only: 8 tools (list_registries, list_packages, list_package_versions, list_lifecycle_rules, get_lifecycle_stats, list_lifecycle_executions, list_artifact_scans, list_package_type_configs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to app.harness.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Harness Artifact Registry. Harness Artifact Registry and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which artifact registries do I have in Harness?"
  • "Which packages are stored in my Harness artifact registries?"
  • "What versions of my packages are in Harness Artifact Registry?"
  • "Which cleanup rules does my Harness artifact registry have?"
  • "How much storage have my Harness artifact cleanup rules reclaimed?"
  • "Did the last Harness artifact cleanup run succeed?"

What it does

  • list_registries: List Artifact Registry registries (virtual and upstream) of an account, organization or project with package type, visibility and last change. Creator and modifier names are left out.
  • list_packages: List packages (container images, Helm charts, npm and Maven packages ...) across registries with type, latest version, registry and quarantine status.
  • list_package_versions: List versions of packages with registry, package type, pull command, quarantine flag and times. Uploader names are left out.
  • list_lifecycle_rules: List artifact retention (lifecycle) rules with action (DELETE or PROTECT), schedule, criteria, scope and last and next run times.
  • get_lifecycle_stats: Get the totals for artifact lifecycle rules: artifacts cleaned, storage reclaimed and runs in the last 30 days.
  • list_lifecycle_executions: List runs of artifact lifecycle rules with status (PENDING, INPROGRESS, SUCCESS, FAILED), trigger type, versions deleted and storage reclaimed.
  • list_artifact_scans: List artifact firewall scan results with scan status (BLOCKED or WARN), violation categories (Security, License, MaliciousPackage ...), package and registry.
  • list_package_type_configs: List which package types (Docker, Helm, npm, Maven ...) the account supports and their capabilities.

BYOK key

You bring your own Harness Artifact Registry Harness personal access token or service account token (https://developer.harness.io/docs/platform/automation/api/add-and-manage-api-keys/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to app.harness.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Only accounts served from app.harness.io are supported; clusters on other Harness hosts are not.

Data sources

Live from the Harness Artifact Registry API (app.harness.io) with a BYOK key; documentation: https://apidocs.harness.io/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Harness Artifact Registry. Harness Artifact Registry and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Harness Artifact Registry account.

Built for: Worldwide. Languages: English.