chore: migrate to mcpb-pack@v3 (drop server.json)#5
Merged
Conversation
mpak now composes the MCP registry's `ServerDetail` discovery shape from `manifest.json` server-side, so the per-bundle `server.json` file is no longer used. Drops it, removes the version-bump step that synced its `version` from `manifest.json`, and bumps the build workflow to `mcpb-pack@v3`. Optional follow-up: add a branded reverse-DNS name override in `manifest.json` under `_meta["dev.mpak/registry"].name` (e.g. `ai.nimblebrain/<name>` for `@nimblebraininc/*` bundles). Without an override the registry uses the mechanical default `dev.mpak.<scope>/<name>`.
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.
Summary
server.jsonfrom this bundle. mpak now composes the MCP registry'sServerDetaildiscovery shape frommanifest.jsonserver-side, so the per-bundle file is unused.server.json::versionfrommanifest.json.NimbleBrainInc/mcpb-pack@v2→@v3in the release workflow.Optional follow-up
Add a branded reverse-DNS name override in
manifest.jsonif you want a non-default registry name:{ "_meta": { "dev.mpak/registry": { "name": "ai.nimblebrain/<bundle-name>" } } }Without an override the registry uses the mechanical default
dev.mpak.<scope>/<name>.Test plan
mcpb-pack@v3https://registry.mpak.dev/v1/servers/<name>after announce