fix(mcp): preserve GitHub org case in mcpName (Mnexa-AI not mnexa-ai)#103
Merged
Conversation
Registry rejected the 0.3.1 publish:
status 403: You have permission to publish: io.github.jiashuoz/*,
io.github.Mnexa-AI/*. Attempting to publish:
io.github.mnexa-ai/mcp-server.
The Registry's publishing-guide example lowercases the org name
("io.github.my-username/...") but its actual permission check is
case-sensitive and preserves the canonical GitHub org slug. Since
our org is `Mnexa-AI` (mixed case), the published name must be
`io.github.Mnexa-AI/mcp-server`, not the lowercased form #101
landed.
Two-line fix in both files. Version bumps 0.3.1 → 0.3.2 because
0.3.1 is already locked on npm with the wrong mcpName — Registry's
verification step reads the live npm manifest and would still
reject if we re-tried at 0.3.1.
Post-merge ceremony stays the same:
git tag mcp-v0.3.2 && git push origin mcp-v0.3.2
# wait for publish-mcp.yml
cd mcp && mcp-publisher publish
Validated against schema 2025-12-11 with the new name.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
MCP Registry rejected the 0.3.1 publish:
The Registry's publishing guide lowercases the org name in its example (`io.github.my-username/...`), but the actual permission engine is case-sensitive and preserves the canonical GitHub org slug. Our org is `Mnexa-AI` (mixed case), so the published name must be `io.github.Mnexa-AI/mcp-server`, not what #101 landed.
What
Two-file diff in both
mcp/package.jsonandmcp/server.json:mcpName/name:io.github.mnexa-ai/mcp-server→io.github.Mnexa-AI/mcp-serverversion(andpackages[0].version):0.3.1→0.3.2The version bump is necessary because 0.3.1 is already locked on npm with the wrong
mcpName. Registry verification reads the live npm manifest and would still reject at 0.3.1 even after the typo fix.Verification
mcp/server.jsonre-validates against schema 2025-12-11 with the new namepackage.json,server.json:version,server.json:packages[0].versionmcp-v0.3.2firing publish-mcp.ymlPost-merge ceremony
🤖 Generated with Claude Code