Skip to main content
Glama
harbor-mcp

harbor-mcp

by si-essence

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP port. Default 3000.3000
HARBOR_URLYesRequired. Origin only, http or https, no userinfo, query, hash, or path. Example: http://127.0.0.1:18080.
MCP_TRANSPORTNostdio or http. --http overrides.
HARBOR_CONTACTNoContact token in the User-Agent. Must not contain the password.
HARBOR_PASSWORDNoRequired unless HARBOR_PASSWORD_FILE is set. Sent as HTTP Basic. Redacted in logs, errors, and results.
HARBOR_USERNAMEYesRequired. Harbor user or robot account (robot$project+name).
HARBOR_PER_MINUTENoLocal request budget. Default 30. Cache hits do not spend it.30
HARBOR_TIMEOUT_MSNoUpstream timeout. Default 20000.20000
HARBOR_ALLOW_WRITESNoMust be the literal true before a confirmed write is sent.
HARBOR_CACHE_TTL_SECNoRead cache TTL. Default 60. Writes clear the cache.60
HARBOR_PASSWORD_FILENoOptional. chmod 600 file whose trimmed contents are the password. Used when HARBOR_PASSWORD is omitted.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
harbor_systemC

Harbor health, ping, search, statistics, systeminfo, volumes, and the current user. Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true. Actions: health, ping, search, statistics, systeminfo, volumes, current_user, current_permissions.

harbor_projectsB

Project list, get, summary, create, update, delete, members, and metadata. Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true. Actions: list, create, get, update, delete, deletable, summary, members_list, members_add, member_get, member_update, member_remove, metadata_list, metadata_add, metadata_get, metadata_update, metadata_delete.

harbor_repositoriesA

Repository list, get, description update, and delete. Repository names with slashes are double-URL-encoded. Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true. Actions: list, list_all, get, update, delete.

harbor_artifactsB

Artifact list and get, tags, artifact labels, vulnerability addition, scan trigger, and delete. Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true. Actions: list, get, delete, tags_list, tag_create, tag_delete, label_add, label_remove, vulns, scan, accessories.

harbor_robotsA

Robot account list, get, create, update, secret refresh, and delete. Create and refresh return secret once in the tool result and never in logs. Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true. Actions: list, create, get, update, refresh_secret, delete.

harbor_adminB

Quotas, labels, GC schedule and history, retention metadata, and webhook policy list. GC schedule writes and label writes are gated. Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true. Actions: quotas_list, quota_get, labels_list, label_create, label_get, label_update, label_delete, gc_schedule, gc_history, gc_schedule_create, gc_schedule_update, retention_metadata, retention_get, webhook_list, webhook_events.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation4/5

The six tools are cleanly split by Harbor domain: system, projects, repositories, artifacts, robots, and admin. There is minor potential overlap around labels and metadata, since artifact labels, project metadata, and global admin labels live in different tools, but the descriptions make the intended boundaries clear.

Naming Consistency5/5

All tool names follow a consistent harbor_<domain> convention, and action names within each tool use snake_case. The pattern is predictable despite grouping multiple actions under each domain tool.

Tool Count5/5

Six domain-oriented tools are a well-scoped surface for a broad Harbor server. Each tool corresponds to a meaningful resource area, and the high action count inside tools like projects/admin is a dispatch design choice rather than excessive top-level tool count.

Completeness3/5

Core Harbor resource workflows are covered: projects, repositories, artifacts, robots, and several admin functions. However, there are notable gaps in admin operations, including webhook CRUD beyond list/events, user management, replication, audit logs, and full quota/retention management.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues