Skip to content

Document the packkit-mcp release process#9

Merged
DanMat merged 1 commit into
mainfrom
docs/mcp-releasing
Jul 21, 2026
Merged

Document the packkit-mcp release process#9
DanMat merged 1 commit into
mainfrom
docs/mcp-releasing

Conversation

@DanMat

@DanMat DanMat commented Jul 21, 2026

Copy link
Copy Markdown
Owner

Writes down how packkit-mcp gets 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.md covers:

  • The five listing surfaces — npm, the official MCP registry, Glama, mcpservers.org, awesome-mcp-servers — and what updates each.
  • The version fields that must agree across mcp/package.json, server.json, and mcp/server.js.
  • Glama's known-good build config. Glama generates its own Dockerfile from the admin form — mcp/Dockerfile is not what it builds — so the working values are recorded.
  • 7 gotchas, each of which cost real debugging time: the registry namespace is case-sensitive (io.github.DanMat, lowercase 403s), mcpName must match byte-for-byte and a wrong one burns an npm version permanently, description is capped at 100 chars, npm publish must precede mcp-publisher publish, E404 from 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.md picks up links to the registry and Glama listings, and points at the new doc.

🤖 Generated with Claude Code

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>
@DanMat
DanMat merged commit 03d23d4 into main Jul 21, 2026
4 checks passed
@DanMat DanMat changed the title docs(mcp): document the packkit-mcp release process Automate packkit-mcp publishing everywhere, and document it Jul 21, 2026
@DanMat DanMat changed the title Automate packkit-mcp publishing everywhere, and document it Document the packkit-mcp release process Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant