Harbor

io.github.oreondev由 GitHub 账号 oreondev 发布v0.1.1更新于 Nov 5, 2026

Read-only access to a Harbor registry: projects, artifacts, vulnerabilities, robots and replication.

发布方自己的服务:Harbor Notes

概览

AI 生成的概览

面向 Harbor 容器镜像仓库的只读 MCP 服务器,让助手查看项目、制品、漏洞、机器人账号与复制状态。

可以做什么
  • 查看仓库本身:版本、认证模式以及服务器所使用的身份
  • 列出项目,并读取单个项目的配额、CVE 白名单、保留与不可变设置
  • 列出仓库与制品,含标签、大小、推送和拉取时间及扫描摘要
  • 获取某个制品的漏洞列表,按严重程度排序
  • 查看访问权限:带角色的项目成员,以及带权限和过期时间的机器人账号
  • 查看复制端点和策略及最近一次运行、Webhook 策略和垃圾回收计划
适用场景
适合让助手回答关于运行中 Harbor 仓库的问题,例如有哪些镜像、哪些制品存在未修复漏洞、谁能访问某个项目,或复制与垃圾回收是否正常,同时不授予写权限。
运行要求
以本地进程通过 stdio 运行,通常使用已发布的容器镜像(Docker)或下载的二进制文件。需要 HARBOR_URL、HARBOR_USERNAME 和 HARBOR_PASSWORD(建议使用只读系统机器人账号)。可选:HARBOR_CA_FILE、HARBOR_INSECURE_SKIP_VERIFY、HARBOR_MCP_RATE,以及 HTTP 模式下的 HARBOR_MCP_HTTP_TOKEN。需要能访问 Harbor 实例的网络。
安装前请注意
需要通过环境变量提供 Harbor 凭据,机器人密钥仅在创建时显示一次。管理员账号也可用,但会给助手远超所需的权限,建议使用只读机器人。HARBOR_INSECURE_SKIP_VERIFY 会关闭对 Harbor 的 TLS 校验。十二个工具均为只读,没有工具会删除任何内容;写操作工具计划仅在显式开启后提供。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Harbor,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Harbor MCP server

A Model Context Protocol server for Harbor, the open-source container registry. It lets AI assistants such as Claude, Cursor and VS Code answer questions about a running Harbor: projects and quotas, repositories and artifacts, vulnerability scan results, robot accounts, replication health and garbage collection.

Documentation: https://www.oreonit.com/harbor-mcp/

This is an independent community project. It is not affiliated with or endorsed by the Harbor project or the CNCF; Harbor is a trademark of The Linux Foundation.

Status

Changes per release are in the release notes. The twelve read tools work over stdio and streamable HTTP, and are tested against a fake Harbor, Harbor 2.15 on every pull request and Harbor 2.12 to 2.15 nightly, as an administrator and as the read-only robot below. The design is in docs/DESIGN.md.

  • Read-only: twelve tools covering projects, repositories, artifacts, vulnerabilities, robots, members, registries, replication, webhooks and garbage collection. Write tools (scan, start replication, add a label, create a project) will come later, only with an explicit opt-in. No tool deletes anything.
  • Secrets stay out of the conversation: Harbor credentials, robot secrets and webhook authorization headers never appear in tool results, logs or errors.
  • stdio for desktop clients, and streamable HTTP with a bearer token for running in a cluster.
  • A signed multi-arch image, ghcr.io/oreondev/harbor-mcp, listed in the official MCP Registry as io.github.oreondev/harbor-mcp.
  • Uses the Harbor client of harbor-resource-operator, the Kubernetes operator that manages Harbor projects, robot accounts and replication as code.

Tools

ToolAnswers
harbor_system_infoHarbor version, authentication mode, and the user or robot the server acts as
harbor_list_projects, harbor_get_projectprojects; quota, CVE allowlist, retention and immutability of one
harbor_list_repositories, harbor_list_artifactsrepositories; artifacts with tags, size, push and pull times and scan summary
harbor_get_vulnerabilitiesthe vulnerabilities of one artifact, worst first
harbor_list_members, harbor_list_robotswho has access: members with roles, robot accounts with permissions and expiry
harbor_list_registries, harbor_list_replicationsreplication endpoints and policies, with the last run
harbor_list_webhooks, harbor_get_gcwebhook policies; the garbage collection schedule

Set up a read-only Harbor identity

Run the server as a system robot account that can only read. docs/read-only-robot.json is the request body for Harbor's API, with the permissions the tools need (the end-to-end tests use the same file):

sh
curl -u admin -H 'Content-Type: application/json' -d @docs/read-only-robot.json \  https://harbor.example.com/api/v2.0/robots

Harbor shows the secret once, in the response; the user name is robot$harbor-mcp. An administrator account also works, but gives the assistant more than it needs.

Use it

Configuration comes from environment variables; each except HARBOR_CA_FILE can instead be read from a file named by <NAME>_FILE, for mounted secrets:

VariableMeaning
HARBOR_URLHarbor base URL, for example https://harbor.example.com (required)
HARBOR_USERNAME, HARBOR_PASSWORDthe robot name and secret (required)
HARBOR_CA_FILEextra CA bundle (PEM) for Harbor's certificate
HARBOR_INSECURE_SKIP_VERIFYtrue to skip TLS verification of Harbor
HARBOR_MCP_RATErequests per second to Harbor, default 10
HARBOR_MCP_HTTP_TOKENbearer token for HTTP mode

One-click install (the client asks for the URL and credentials, or you fill them in afterwards):

[Install in VS Code] [Add to Cursor]

Claude Code, with the image (replace 0.1.1 with the latest release):

sh
claude mcp add harbor -e HARBOR_URL=https://harbor.example.com -e 'HARBOR_USERNAME=robot$harbor-mcp' -e HARBOR_PASSWORD=... \  -- docker run -i --rm -e HARBOR_URL -e HARBOR_USERNAME -e HARBOR_PASSWORD ghcr.io/oreondev/harbor-mcp:0.1.1

Claude Desktop, Cursor and other clients that read an mcpServers file:

json
{  "mcpServers": {    "harbor": {      "command": "docker",      "args": ["run", "-i", "--rm", "-e", "HARBOR_URL", "-e", "HARBOR_USERNAME", "-e", "HARBOR_PASSWORD",               "ghcr.io/oreondev/harbor-mcp:0.1.1"],      "env": {        "HARBOR_URL": "https://harbor.example.com",        "HARBOR_USERNAME": "robot$harbor-mcp",        "HARBOR_PASSWORD": "..."      }    }  }}

Without Docker, download a binary from the releases (or go install github.com/oreondev/harbor-mcp/cmd/harbor-mcp@latest) and use harbor-mcp as the command.

HTTP mode

For a shared server, for example a Deployment next to Harbor, start it with -http and a token:

sh
docker run -d -p 8080:8080 -e HARBOR_URL -e HARBOR_USERNAME -e HARBOR_PASSWORD -e HARBOR_MCP_HTTP_TOKEN \  ghcr.io/oreondev/harbor-mcp:0.1.1 -http :8080claude mcp add --transport http harbor https://harbor-mcp.example.com/mcp -H "Authorization: Bearer $HARBOR_MCP_HTTP_TOKEN"

MCP is served at /mcp and every request needs the token; GET /healthz is open for probes. Without a token the server only listens on a loopback address. Put TLS in front of it (an ingress or a mesh).

Verify the image

sh
cosign verify ghcr.io/oreondev/harbor-mcp:0.1.1 \  --certificate-identity-regexp '^https://github.com/oreondev/harbor-mcp/\.github/workflows/release\.yml@' \  --certificate-oidc-issuer https://token.actions.githubusercontent.com

Maintainers

Maintained by Oreon IT. Issues and pull requests are welcome.

Security

Report vulnerabilities privately; see SECURITY.md.

Licence

Apache-2.0.

来源:README.md,提交 d4b969f

工具

0
SourceWeft 曾在隔离沙箱中以无凭据方式启动该软件包一次,以列出其工具,但未能完成:该软件包类型无法在沙箱中运行。

版本历史

2
  1. v0.1.1最新Nov 5, 2026
  2. v0.1.0Nov 5, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Harbor 集成