Repository navigation
Add MCPB packaging and MCP Registry server.json - #1
Merged
Merged
Conversation
Signed-off-by: Aniket <aniketkomailkro@gmail.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
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.
Prepare prom-mcp for the official MCP Registry.
mcpb/manifest.json(spec v0.3, binary server type, Prometheus URL, token, and timeout as user config) andmcpb/build.sh, which builds one.mcpbbundle per platform intodist/with reproducible bytes.server.jsonforio.github.aniketatgithub/prom-mcppointing at the four bundles as GitHub release assets, with SHA-256 hashes from a local build. Passesmcp-publisher validate.checksums.txtcovers both.distribution/registry-publish.mddocuments the one remaining manual step: verify the hashes against the release, thenmcp-publisher login githubandmcp-publisher publish. The login is interactive, so publishing stays a human step.Verified locally:
go build ./...,go vet ./..., andgo test ./...are green, the manifest passesmcpb validate, and the bundled linux/amd64 binary answers initialize and tools/list over stdio.