Repository navigation
Add Google Artifact Registry as docker registry #427
Description
Is your feature request related to a problem? Please describe.
Our server is deployed in GAR. As of now, it seems like MCP registry only supports the official Docker registry.
Describe the solution you'd like
Supporting GAR.
"registry_type": "oci",
"registry_base_url": "https://artifactregistry.googleapis.com",
"identifier": "<region>-docker.pkg.dev/<repo>/...",
"version": "1.0.0",
"file_sha256": "filesha256",
"tag": "latest", // it will be great to support tag as well.
Describe alternatives you've considered
N/A
Additional context
N/A
Activity
domdomegg commentedon Sep 11, 2025
Sounds good! Same probably applies as for GHCR here: #393
[-]Support Google Artifact Registry as package registry[/-][+]Support Google Artifact Registry as docker registry[/+][-]Support Google Artifact Registry as docker registry[/-][+]Add Google Artifact Registry as docker registry[/+]feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
feat: add support for multiple OCI registries (modelcontextprotocol#393…
10 remaining items
rdimitrov commentedon Oct 20, 2025
I’ve been thinking about this more and started a thread on Discord whether we should use this opportunity to switch to a client library like
go-containerregistrywhich would enable us support all OCI-compliant registries. I'll post a message afterwards sharing any potential decisions 👍Yuan325 commentedon Oct 22, 2025
@domdomegg Yeap! Here's the image identifier: us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:latest
@rdimitrov Yes, our image is in a registry that allow read from
allUsers. And yes, it shouldn't need any authentication to access the image itself. Thanks for sharing the thread and the updates! greatly appreciated!Add support for Google Artifact Registry (GAR) (#692)
rdimitrov commentedon Oct 28, 2025
@Yuan325 - The PR adding support for GAR got merged, so if you're interested it would be nice to confirm it works for you 👍
It should be available in staging - https://staging.registry.modelcontextprotocol.io/docs
feat(mcp-registry): publish custom tools server to mcp-registry (#1834)
deploy: feat(mcp-registry): publish custom tools server to mcp-regist…
deploy: feat(mcp-registry): publish custom tools server to mcp-regist…
feat(mcp-registry): publish custom tools server to mcp-registry (#1834)
feat(mcp-registry): publish custom tools server to mcp-registry (#1834)
Add support for Google Artifact Registry (GAR) (modelcontextprotocol#692
Add support for Google Artifact Registry (GAR) (modelcontextprotocol#692
feat(mcp-registry): publish custom tools server to mcp-registry (#1834)
rdimitrov commentedon Oct 11, 2026
Closing as completed