docs: Docker MCP Registry PR submitted (roadmap 21.2) - #311
Merged
Conversation
Fork + PR sent: docker/mcp-registry#4689. Updates: - server.yaml: about.title changed MCPg -> PostgreSQL. Their validator (go run ./cmd/validate) rejects any title containing the literal substring "MCP" (case-sensitive) -- not documented anywhere, only caught by actually running their validator. Description still says "MCPg" freely; only the title field is checked. - server.yaml: source.commit re-pinned to main's tip at submission time (0ed672b, post-#309/#310) rather than the commit drafted alongside 21.1's tools.json generator. - feature-shortlist.md / CHANGELOG.md: mark 21.1/21.2 shipped, link the open PR, note 21.3 (254-tool surface size) as the next active work item. Advances roadmap row: 21.2 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PdN8kDW5Yc8rFb6scthKef
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docker MCP Registry submission (roadmap §21) sent: docker/mcp-registry#4689.
What changed
packaging/docker-mcp-registry/server.yaml:about.titlechangedMCPg→PostgreSQL. Their validator (go run ./cmd/validate) rejects any title containing the literal substringMCP(case-sensitive) — not documented anywhere, only caught by actually running the validator against a real fork. The description field still says "MCPg" freely; onlytitleis checked.source.commitre-pinned tomain's tip at submission time (0ed672b, post-ci: clear zizmor baseline — scope id-token, persist-credentials: false #309/chore: prep Docker MCP Registry submission (roadmap 21.1) #310) rather than the commit drafted alongside 21.1's generator.docs/feature-shortlist.md: 21.1 and 21.2 marked shipped with the PR link; 21.3 (254-tool surface size, no bucket/filter env var today) called out as the next active work item.CHANGELOG.md: submission entry added under[Unreleased].Verification (against a real fork + the registry's own toolchain)
go run ./cmd/validate --name mcpg— all checks pass (name, directory, title, YAML formatting vianpx prettier, pinned commit, secrets, config env, license, icon).go run ./cmd/build --tools mcpg— image built asmcp/mcpg, 254 tools found (confirms the checked-intools.jsonbypass works end-to-end).go run ./cmd/catalog mcpg— test catalog generated successfully.Advances roadmap row: 21.2
Summary by Sourcery
Update Docker MCP Registry packaging metadata and mark the registry submission as shipped in project docs.
Enhancements: