feat(phase-5): v0.3.1 — add mcpName for MCP Registry#15
Merged
Conversation
Tiny bump to enable MCP Registry submission (modelcontextprotocol/registry): - mcp-server/package.json gains `mcpName: io.github.sonpiaz/watch-cli` per https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/quickstart.mdx Required for GitHub-based ownership verification of the npm package. - lib/version.sh and mcp-server/package.json both bumped 0.3.0 -> 0.3.1. No code changes. Tagging v0.3.1 after this merges will: 1. Republish @sonpiaz/watch-cli-mcp@0.3.1 to npm with the mcpName field. 2. (Manual follow-up by maintainer) Run `mcp-publisher publish` to register the server in https://registry.modelcontextprotocol.io — that step needs interactive GitHub OAuth login and cannot run from CI yet. Co-Authored-By: Claude Opus 4.7 (1M context) <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
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
Two-line change to enable submission to the official MCP Server Registry (replaces the retired third-party list in `modelcontextprotocol/servers` README).
The `mcpName` field is the GitHub-based ownership verification mechanism required by the MCP registry. It must start with `io.github./` to prove the npm publisher controls the matching GitHub account.
Post-merge sequence (maintainer)
Once steps 1–5 complete, the server appears in registry.modelcontextprotocol.io and is discoverable by every MCP-capable agent that consumes the registry.
Why this isn't done by CI
The publish step needs interactive GitHub OAuth. Automating it would require a long-lived OAuth token, which mcp-publisher does not yet support. Once the registry exposes a CI-friendly token flow, the release workflow can chain step 5.
Test plan