mcpField
H
harbor-registry-mcp

harbor-registry-mcp

Local
github.com/mshegolevCloud & Infra1Updated 11w ago

About harbor-registry-mcp

harbor-registry-mcp is an MCP server for Harbor 2.x, aimed at DevOps teams inspecting projects, artifacts, and storage or planning cleanup. It adds storage reports and cleanup candidates, with bulk deletion set to dry-run by default.

Key features

  1. 01List projects, repositories, and artifacts
  2. 02Generate project storage reports
  3. 03Find artifact cleanup candidates
  4. 04Delete individual or bulk artifacts
  5. 05Default bulk cleanup to dry-run

Use cases

  1. 01Review image storage use by project
  2. 02Find untagged or old artifacts
  3. 03Preview cleanup while keeping recent versions

MCP support

The server exposes Harbor project, repository, artifact, and cleanup tools to MCP clients over stdio. Delete tools are marked destructive, and bulk deletion defaults to dry-run.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"mshegolev-harbor-registry": {
"command": "uvx",
"args": [
"harbor-registry-mcp"
],
"env": {
"HARBOR_URL": "<HARBOR_URL>",
"HARBOR_USERNAME": "<HARBOR_USERNAME>",
"HARBOR_PASSWORD": "<HARBOR_PASSWORD>",
"HARBOR_SSL_VERIFY": "<HARBOR_SSL_VERIFY>"
}
}
}
}
Run commanduvx harbor-registry-mcp
Environment variables to set
HARBOR_URLHarbor URL (e.g. https://harbor.example.com)
HARBOR_USERNAMEHarbor username (robot account recommended for automation)
HARBOR_PASSWORDSecretHarbor password or robot account token
HARBOR_SSL_VERIFYVerify SSL certificates (true/false). Set to 'false' for self-signed certs.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiharbor-registry-mcp0.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

harbor-registry-mcp

PyPI Python License: MIT

MCP server for Harbor Registry. Lets an LLM agent (Claude Code, Cursor, OpenCode, etc.) list projects, repositories and artifacts, run storage reports, find cleanup candidates, and delete untagged or old artifacts — all with safety rails (dry-run by default for bulk delete).

Python, FastMCP, stdio transport.

Works with any Harbor 2.x instance — SaaS or self-hosted / on-prem.

Why another Harbor MCP?

A couple of community Harbor MCPs exist (nomagicln/mcp-harbor, bupd/harbor-mcp-server) but they expose only the basic list/get endpoints. This one adds storage reports, cleanup candidates, delete untagged, and delete old artifacts with dry-run — the operations DevOps engineers actually need to reclaim disk space.

Design highlights

  • Tool annotations — read-only tools get readOnlyHint: True; destructive ones (harbor_delete_*) carry destructiveHint: True so MCP clients ask for confirmation.
  • Dry-run by default on both bulk cleanups (harbor_delete_untagged, harbor_delete_old_artifacts) — the agent must pass dry_run=False to execute.
  • Structured output — every tool returns a typed payload (TypedDict) + a markdown summary.
  • Structured errors — 401 / 403 / 404 / 429 / 5xx mapped to actionable hints.
  • Pydantic input validation for every argument.
  • Vulnerability snapshot — harbor_list_artifacts surfaces scan status and counts if with_scan_overview is enabled.

Features (8 tools)

Discovery & inspection

  • harbor_list_projects — projects with repo counts and visibility
  • harbor_list_repos — repositories in a project
  • harbor_list_artifacts — artifacts in a repository with tags/size/scan status
  • harbor_storage_report — full project storage breakdown (all repos × all artifacts)

Cleanup planning

  • harbor_cleanup_candidates — suggest what to delete (untagged, never-pulled, old versions)

Cleanup execution (destructive)

  • harbor_delete_artifact — delete a single artifact by tag or digest
  • harbor_delete_untagged — delete all untagged artifacts in a project/repo (dry-run default)
  • harbor_delete_old_artifacts — keep N latest per repo, delete the rest (dry-run default)

Installation

Requires Python 3.10+.

# via uvx (recommended)
uvx --from harbor-registry-mcp harbor-registry-mcp

# or via pipx
pipx install harbor-registry-mcp

Configuration

claude mcp add harbor -s project \
  --env HARBOR_URL=https://harbor.example.com \
  --env HARBOR_USERNAME='robot$your-robot' \
  --env HARBOR_PASSWORD=your-robot-token \
  --env HARBOR_SSL_VERIFY=true \
  -- uvx --from harbor-registry-mcp harbor-registry-mcp

Or in .mcp.json:

{
  "mcpServers": {
    "harbor": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "harbor-registry-mcp", "harbor-registry-mcp"],
      "env": {
        "HARBOR_URL": "https://harbor.example.com",
        "HARBOR_USERNAME": "robot$your-robot",
        "HARBOR_PASSWORD": "${HARBOR_PASSWORD}",
        "HARBOR_SSL_VERIFY": "true"
      }
    }
  }
}

Check:

claude mcp list
# harbor: uvx --from harbor-registry-mcp harbor-registry-mcp - ✓ Connected

Environment variables

VariableRequiredDescription
HARBOR_URLyesHarbor URL (no trailing slash)
HARBOR_USERNAMEyesHarbor username — robot account recommended
HARBOR_PASSWORDyesPassword or robot token
HARBOR_SSL_VERIFYnotrue/false. Default: true.

Example usage

  • "Storage report for project einvy-pub"
  • "Find cleanup candidates in qa-assistant — keep latest 3"
  • "Delete all untagged artifacts in qa-assistant"
  • "Dry-run delete of old artifacts in qa-assistant/pgvector-rag, keep 1 latest"
  • "What's in einvy-pub/my-image?"

Safety

  • Read tools use readOnlyHint: True — no confirmation needed.
  • Delete tools use destructiveHint: True — clients should confirm.
  • harbor_delete_untagged and harbor_delete_old_artifacts both default to dry_run=True; the agent must explicitly set dry_run=False to actually delete.
  • harbor_cleanup_candidates is read-only — it only suggests candidates, never deletes.

Development

git clone https://github.com/mshegolev/harbor-registry-mcp.git
cd harbor-registry-mcp
pip install -e '.[dev]'
pytest

License

MIT © Mikhail Shchegolev

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.