fix(registry): add required per-package transport to server.json#23
Merged
Conversation
The 2025-09-29 MCP server schema requires a `transport` object on each
package (validated locally against the published schema). server.json
declared a top-level `transports` array, which the schema ignores, so the
registry publish failed: packages[0].transport missing / unsupported type "".
Move it to packages[0].transport = { "type": "stdio" } and drop the invalid
root array. Completes the registry-publish fix begun in the identifier/
registryType change.
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.
Second (and final) registry-schema fix. After identifier/registryType, the 2025-09-29 schema flagged
packages[0].transportmissing. Moved transport into the package ({ "type": "stdio" }) and dropped the invalid roottransportsarray. Validated locally against the published schema (jsonschema, Draft 2020-12) — passes clean, so the v1.0.6 registry publish will succeed. npm + GitHub Releases already current through 1.0.5; this closes the registry gap.