repo: move MCP Registry namespace to io.github.oceanmodeling after the transfer - #123
Merged
Merged
Conversation
…e transfer The registry publish step in publish.yml authenticates with GitHub OIDC, which only grants the io.github.<repository_owner> namespace. Since the repo now lives under oceanmodeling, every server.json still named io.github.mansurjisan/<server> would be rejected on the next tagged release, and the registry's PyPI ownership check looks for a matching mcp-name marker in the package README. Rename the 18 server.json entries and the 18 README mcp-name comments to io.github.oceanmodeling/<server>, and point the README registry badge at the org. No code changes; the existing entries under the old namespace stay active until each server is re-released under the new one.
mansurjisan
added a commit
that referenced
this pull request
Sep 4, 2026
) Metadata-only release. The wheel picks up the project URLs that now point at github.com/oceanmodeling/ocean-mcp (#120) and the README mcp-name marker io.github.oceanmodeling/coops-mcp (#123), and the registry step publishes the first entry under the org namespace. This is the canary for the transferred publish pipeline: it exercises the re-pointed PyPI trusted publisher and the org-owned registry namespace end to end before any other server is released.
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
1 participant
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.
Why
publish.ymllogs into the MCP Registry with GitHub OIDC (mcp-publisher login github-oidc), which grants only theio.github.<repository_owner>namespace. After the transfer tooceanmodeling, everyserver.jsonstill namedio.github.mansurjisan/<server>would fail the registry step on the next tagged release. The registry also verifies PyPI package ownership by looking for a matching<!-- mcp-name: ... -->marker in the package README, so both must change together.This is section 4 of the transfer runbook; PR #120 covered the
github.comURLs but left the namespace.What
servers/<name>/server.json:name->io.github.oceanmodeling/<name>servers/<name>/README.md:mcp-namemarker ->io.github.oceanmodeling/<name>README.md: MCP Registry badge now links to?q=oceanmodeling37 one-line changes, no code. Verified all 18
server.jsonfiles still parse and carry the new prefix;git grep mansurjisanreturns nothing.Notes
io.github.mansurjisan/*stay active and are unaffected. Each server appears under the org namespace only after its next release (PyPI publish first, then registry), so the badge link is empty until the first post-transfer release.oceanmodelingowner (runbook section 3); that is a PyPI-side setting, not a repo change.