feat: publish to MCP Registry on release (v1.8.1)#127
Merged
Conversation
- Add server.json with namespace io.github.freema/mcp-gsheets (npm only) - Add README ownership marker for mcp-publisher namespace verification - Add mcpName field to package.json (required by registry validation) - Add publish-mcp-registry workflow (release: published + workflow_dispatch) - Bump version to 1.8.1 so npm release picks up the mcpName field
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
1 participant
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.
Summary
server.jsonat repo root with namespaceio.github.freema/mcp-gsheets(npm package only — no GHCR/OCI distribution).<!-- mcp-name: io.github.freema/mcp-gsheets -->ownership marker to README somcp-publishercan verify the namespace.mcpNamefield topackage.json— required by registry validation when it inspects the published npm package..github/workflows/publish-mcp-registry.yml(runs onrelease: publishedandworkflow_dispatch). Waits for npm package availability before callingmcp-publisher publish. Authenticates via GitHub OIDC — no secrets needed forio.github.freema/*namespace.1.8.1so the next npm publish carries themcpNamefield (registry rejects packages without it).Why now
The official MCP Registry (registry.modelcontextprotocol.io) is the canonical discovery channel for MCP clients (Claude.ai, Cursor, VS Code, Windsurf). Publishing makes the server installable through their built-in catalogs.
Test plan
v1.8.1—release.ymlbuilds + creates GitHub release,publish.ymlpublishes to npm (already triggers ontags: 'v*.*.*').1.8.1is live, rungh workflow run publish-mcp-registry.yml --ref main.Notes
server.json— this repo doesn't push to GHCR. Add later if a Docker image is published.release.yml(viaGITHUB_TOKEN) do not trigger downstream workflows. That's why the MCP Registry publish needs to be triggered manually after npm goes live, ORrelease.ymlneeds to use a PAT instead.