Repository navigation
ci: publish to the MCP Registry from CI, check version bumps - #2
Merged
Merged
Conversation
- publish-mcp.yml: on a push to main that changes server.json, by hand, or on a v<version> tag that must equal server.json. server.json's version is the one published. Already published with the same content -> no-op; same version with different content -> fails with "bump version". DNS auth for the domain derived from the namespace; MCP_PRIVATE_KEY (org secret) accepted as PEM or hex seed and checked against the apex TXT record before login. - validate-server-json.yml: every PR - schema, comparison with the registry, npm release + mcpName for npm-backed servers, and a plugin.json version bump when the plugin changed. Weekly run fails while npm is ahead of server.json. - .github/scripts/: the checks, identical across all MCP setup repos. - .claude/CLAUDE.md: when and how to bump each version, how publishing and the registry key work. Under .claude/ because a CLAUDE.md at the plugin root draws a `claude plugin validate` warning and is never loaded from the plugin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014kBzcE2sPohiNhWGtyAJ1w
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.
Publishes
server.jsonto the MCP Registry from CI and catches forgotten version bumps before they reachmain.Publish (
publish-mcp.yml) — on a push tomainthat changesserver.json, by hand (Run workflow), or on av<version>tag that must equalserver.json. The version inserver.jsonis what gets published:Auth: DNS for the domain derived from the namespace (
dev.dudko→dudko.dev). Org secretMCP_PRIVATE_KEYis accepted as the PEM file or the hex seed; the job derives the public key and checks it against the apex TXT record beforemcp-publisher login, so a wrong or missing key fails with a plain message.Validate (
validate-server-json.yml) — every PR: schema; comparison with what the registry serves; new version must be above the latest published; for npm-backed servers the release must exist withmcpName; a plugin change needs a newplugin.jsonversion (installed plugins are pinned to it). Weekly run on top..claude/CLAUDE.md— the bump rules and how publishing/the key work, so Claude bumps versions in the same change. It sits under.claude/because aCLAUDE.mdat the plugin root (this repo is the plugin,source: ./) draws aclaude plugin validatewarning and isn't loaded from the plugin anyway.Merging this publishes nothing:
server.jsonis unchanged and the registry already serves it as is.Generated by Claude Code