Harbor MCP Server
Provides read-only tools for querying a running Harbor container registry, including projects and quotas, repositories and artifacts, vulnerability scan results, members and robot accounts, registries and replication policies, webhooks, and garbage collection status.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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.
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
Version 0.1.0 is the first release. 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 asio.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.
Related MCP server: Harbor MCP Server
Tools
Tool | Answers |
| Harbor version, authentication mode, and the user or robot the server acts as |
| projects; quota, CVE allowlist, retention and immutability of one |
| repositories; artifacts with tags, size, push and pull times and scan summary |
| the vulnerabilities of one artifact, worst first |
| who has access: members with roles, robot accounts with permissions and expiry |
| replication endpoints and policies, with the last run |
| webhook 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):
curl -u admin -H 'Content-Type: application/json' -d @docs/read-only-robot.json \
https://harbor.example.com/api/v2.0/robotsHarbor 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:
Variable | Meaning |
| Harbor base URL, for example |
| the robot name and secret (required) |
| extra CA bundle (PEM) for Harbor's certificate |
|
|
| requests per second to Harbor, default 10 |
| bearer token for HTTP mode |
Claude Code, with the image (replace 0.1.0 with the latest release):
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.0Claude Desktop, Cursor and other clients that read an mcpServers file:
{
"mcpServers": {
"harbor": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "HARBOR_URL", "-e", "HARBOR_USERNAME", "-e", "HARBOR_PASSWORD",
"ghcr.io/oreondev/harbor-mcp:0.1.0"],
"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:
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.0 -http :8080
claude 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
cosign verify ghcr.io/oreondev/harbor-mcp:0.1.0 \
--certificate-identity-regexp '^https://github.com/oreondev/harbor-mcp/\.github/workflows/release\.yml@' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comMaintainers
Maintained by Oreon IT. Issues and pull requests are welcome.
Security
Report vulnerabilities privately; see SECURITY.md.
Licence
This server cannot be deployed
Maintenance
Related MCP Connectors
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Read-only AI access to HAVN properties, leads, tasks, files, media, and analytics.
Read-only tools: App Store customer reviews and Docker Hub repo metadata.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceEnables LLMs to search Docker Hub repositories, discover container images, and manage Docker Hub repositories and tags through natural language queries. Supports both public content access and authenticated operations with Docker Personal Access Tokens.171Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI models to interact with Harbor container registries to manage projects, repositories, and system configurations in real time. It provides a suite of tools for monitoring health, retrieving statistics, and performing searches across registry data.41 npm6MIT
- AlicenseAqualityCmaintenanceCP server for Harbor Registry — projects, repositories, artifacts, storage reports, cleanup candidates. Works with any Harbor 2.x instance.868 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables interacting with a Harbor container registry through the Model Context Protocol, supporting operations for projects, repositories, tags, and Helm charts.5 npm1MIT