Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read-only access to a Harbor registry: projects, artifacts, vulnerabilities, robots and replication.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD, HARBOR_INSECURE_SKIP_VERIFY, HARBOR_MCP_RATEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"harbor": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HARBOR_URL",
"-e",
"HARBOR_USERNAME",
"-e",
"HARBOR_PASSWORD",
"-e",
"HARBOR_INSECURE_SKIP_VERIFY",
"-e",
"HARBOR_MCP_RATE",
"ghcr.io/oreondev/harbor-mcp:0.1.1"
],
"env": {
"HARBOR_URL": "your-value",
"HARBOR_USERNAME": "your-value",
"HARBOR_PASSWORD": "your-value",
"HARBOR_INSECURE_SKIP_VERIFY": "your-value",
"HARBOR_MCP_RATE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add harbor --env HARBOR_URL=your-value --env HARBOR_USERNAME=your-value --env HARBOR_PASSWORD=your-value --env HARBOR_INSECURE_SKIP_VERIFY=your-value --env HARBOR_MCP_RATE=your-value -- docker run -i --rm -e HARBOR_URL -e HARBOR_USERNAME -e HARBOR_PASSWORD -e HARBOR_INSECURE_SKIP_VERIFY -e HARBOR_MCP_RATE ghcr.io/oreondev/harbor-mcp:0.1.1Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"harbor": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HARBOR_URL",
"-e",
"HARBOR_USERNAME",
"-e",
"HARBOR_PASSWORD",
"-e",
"HARBOR_INSECURE_SKIP_VERIFY",
"-e",
"HARBOR_MCP_RATE",
"ghcr.io/oreondev/harbor-mcp:0.1.1"
],
"env": {
"HARBOR_URL": "your-value",
"HARBOR_USERNAME": "your-value",
"HARBOR_PASSWORD": "your-value",
"HARBOR_INSECURE_SKIP_VERIFY": "your-value",
"HARBOR_MCP_RATE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"harbor": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HARBOR_URL",
"-e",
"HARBOR_USERNAME",
"-e",
"HARBOR_PASSWORD",
"-e",
"HARBOR_INSECURE_SKIP_VERIFY",
"-e",
"HARBOR_MCP_RATE",
"ghcr.io/oreondev/harbor-mcp:0.1.1"
],
"env": {
"HARBOR_URL": "your-value",
"HARBOR_USERNAME": "your-value",
"HARBOR_PASSWORD": "your-value",
"HARBOR_INSECURE_SKIP_VERIFY": "your-value",
"HARBOR_MCP_RATE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
HARBOR_INSECURE_SKIP_VERIFY envHARBOR_MCP_RATE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account oreondev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: HARBOR_URL, HARBOR_USERNAME, HARBOR_PASSWORD
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
ghcr.io/oreondev/harbor-mcp, listed in the official MCP Registry as io.github.oreondev/harbor-mcp.| Tool | Answers |
|---|---|
harbor_system_info | Harbor version, authentication mode, and the user or robot the server acts as |
harbor_list_projects, harbor_get_project | projects; quota, CVE allowlist, retention and immutability of one |
harbor_list_repositories, harbor_list_artifacts | repositories; artifacts with tags, size, push and pull times and scan summary |
harbor_get_vulnerabilities | the vulnerabilities of one artifact, worst first |
harbor_list_members, harbor_list_robots | who has access: members with roles, robot accounts with permissions and expiry |
harbor_list_registries, harbor_list_replications | replication endpoints and policies, with the last run |
harbor_list_webhooks, harbor_get_gc | webhook policies; the garbage collection schedule |
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/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.
Configuration comes from environment variables; each except HARBOR_CA_FILE can instead be read from a file named by _FILE, for mounted secrets:
| Variable | Meaning |
|---|---|
HARBOR_URL | Harbor base URL, for example https://harbor.example.com (required) |
HARBOR_USERNAME, HARBOR_PASSWORD | the robot name and secret (required) |
HARBOR_CA_FILE | extra CA bundle (PEM) for Harbor's certificate |
HARBOR_INSECURE_SKIP_VERIFY | true to skip TLS verification of Harbor |
HARBOR_MCP_RATE | requests per second to Harbor, default 10 |
HARBOR_MCP_HTTP_TOKEN | bearer token for HTTP mode |
One-click install (the client asks for the URL and credentials, or you fill them in afterwards):
Claude Code, with the image (replace 0.1.1 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.1
Claude 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.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.
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.1 -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).
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
Maintained by Oreon IT. Issues and pull requests are welcome.
Report vulnerabilities privately; see SECURITY.md.
Apache-2.0.