fix(registry): correct server.json schema for MCP registry publish#20
Merged
Conversation
mcp-publisher 1.7.6 / the 2025-09-29 schema require `registryType` and
`identifier`; server.json still used the old `registry`/`name` keys, so the
registry publish 422'd ("identifier"/"registryType" empty) on every release.
Also sync packages[].version (was stuck at 1.0.0) so release-please bumps it
with the top-level version going forward.
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.
Problem
Every release's Publish to MCP official registry step 422'd:
server.jsonused the old registry keys (registry/name); mcp-publisher 1.7.6 + the 2025-09-29 schema requireregistryType/identifier. The step iscontinue-on-error, so releases stayed green but the server never landed in the official MCP registry.packages[].versionwas also stuck at1.0.0.Fix
registry→registryType,name→identifier, addregistryBaseUrl.packages[].versionto the current release so release-please bumps it with the top-level version.Why this cuts 1.0.5
mcp-publisher publishes from the checked-out tag, so the corrected server.json only takes effect in a new tagged release. 1.0.5 will be the first version to land in the registry — and a full green end-to-end run of the now-fixed pipeline.
npm + GitHub Releases are already current through 1.0.4; this closes the registry gap.