ci(release): automate MCP Registry publishing via GitHub Actions OIDC

[stevenobiajulu]

Summary

• Adds publish-mcp-registry job to the release workflow, running in parallel after npm publish with continue-on-error: true
• Uses GitHub Actions OIDC auth (no secrets needed) to publish server.json to registry.modelcontextprotocol.io
• Fixes repository.subfolder in server.json from packages/docx-mcp to packages/safe-docx
• Updates release runbook with new job diagram, verify checklist item, automation note, and troubleshooting section

Design

• Soft-fail: MCP Registry is preview — job failures show yellow but don't block the release
• npm propagation wait: Polls version + mcpName fields (6 attempts, ~150s backoff) before publishing
• Architecture-tolerant: Uses uname for binary download instead of hardcoding linux_amd64
• Idiomatic binary handling: Adds mcp-publisher to $GITHUB_PATH, uses positional server.json arg

Test plan

• YAML validates (python3 -c "import yaml; yaml.safe_load(open('.github/workflows/release.yml'))")
• Merge, bump to 0.8.2, tag and push — verify publish-mcp-registry job in Actions
• Check registry: curl -s "https://registry.modelcontextprotocol.io/server/io.github.UseJunior/safe-docx" | jq .version

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
site	Ready	Preview, Comment	Apr 3, 2026 8:49pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!