Document the packkit-mcp release process#9
Merged
Merged
Conversation
Publishing the MCP server touches four surfaces (npm, the official MCP registry, Glama, and the awesome-mcp-servers listing) and several steps fail in non-obvious ways. Capture the whole process while it's fresh: - which listings exist and what updates each - the four version values that must stay in sync (package.json, mcpName, server.json x2, server.js) - what release.yml already automates (npm) vs what stays manual (server.json, mcp-publisher, Glama rebuild) - the known-good Glama build config (Glama generates its own Dockerfile; mcp/Dockerfile is not what it builds) - gotchas: case-sensitive io.github.DanMat namespace, mcpName ownership check, the 100-char description limit, npm-before-registry ordering, and E404-on-publish actually meaning expired npm auth Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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.
Writes down how
packkit-mcpgets published and to every place it's listed, because several of these steps fail in non-obvious ways and we rediscovered each of them the hard way.mcp/RELEASING.mdcovers:mcp/package.json,server.json, andmcp/server.js.mcp/Dockerfileis not what it builds — so the working values are recorded.io.github.DanMat, lowercase 403s),mcpNamemust match byte-for-byte and a wrong one burns an npm version permanently,descriptionis capped at 100 chars, npm publish must precedemcp-publisher publish,E404from npm usually means expired auth rather than a missing package, and awesome-mcp-servers requires a passing Glama listing plus the score badge.mcp/README.mdpicks up links to the registry and Glama listings, and points at the new doc.🤖 Generated with Claude Code