Skip to content

fix: get packkit-mcp publishing to the official MCP registry (0.1.3)#7

Merged
DanMat merged 2 commits into
mainfrom
fix/registry-description
Jul 20, 2026
Merged

fix: get packkit-mcp publishing to the official MCP registry (0.1.3)#7
DanMat merged 2 commits into
mainfrom
fix/registry-description

Conversation

@DanMat

@DanMat DanMat commented Jul 20, 2026

Copy link
Copy Markdown
Owner

Fixes to make mcp-publisher publish succeed:

  • description trimmed to ≤ 100 chars (registry 422)
  • namespace casing: io.github.DanMat/packkit-mcp (registry namespace is case-sensitive → io.github.DanMat/*); aligned server.json name + package mcpName
  • bump to 0.1.3: npm 0.1.2 already shipped the lowercase mcpName and can't be overwritten, so a fresh publish is needed to carry the correct one

Publish (after this is on your working tree — it already is)

cd mcp && npm publish && cd ..
mcp-publisher publish

🤖 Generated with Claude Code

DanMat and others added 2 commits July 20, 2026 17:35
mcp-publisher rejected 0.1.2 with a 422: description must be <= 100 chars.
Shorten it so the official-registry publish validates.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
….1.3

The registry namespace is case-sensitive: permission is io.github.DanMat/*,
but we used lowercase. Align server.json name + package mcpName to
io.github.DanMat/packkit-mcp. Since npm 0.1.2 baked in the lowercase mcpName
(and can't be overwritten), bump to 0.1.3 so a fresh npm publish carries the
correct mcpName for ownership verification.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@DanMat DanMat changed the title fix(server.json): trim description to registry's 100-char limit fix: get packkit-mcp publishing to the official MCP registry (0.1.3) Jul 20, 2026
@DanMat
DanMat merged commit 86c9be9 into main Jul 20, 2026
4 checks passed
@DanMat
DanMat deleted the fix/registry-description branch July 21, 2026 17:19
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