Publish to the official MCP registry on release#9
Merged
Conversation
Add server.json (io.pasteapp/paste) and the package.json `mcpName` field so the registry can validate the @pasteapp/mcp package against the server name. Bump to 0.1.2. Extend release.yml to publish the listing after the npm publish: sync server.json's version to package.json, install mcp-publisher, login via pasteapp.io domain auth (MCP_REGISTRY_PRIVATE_KEY secret), and mcp-publisher publish. Co-Authored-By: Claude Opus 4.8 (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.
Lists
@pasteapp/mcpon the official MCP registry (registry.modelcontextprotocol.io) asio.pasteapp/paste, published automatically on each GitHub release.Changes
package.json— add"mcpName": "io.pasteapp/paste"(the registry validates the published npm package against the server name via this field) and bump0.1.1 → 0.1.2.server.json(new, repo root) — the registry metadata: nameio.pasteapp/paste, npm package@pasteapp/mcp,transport.type: stdio(local server — not aremotesURL),repository,websiteUrl. Validated against the 2025-12-11 schema (description ≤100 chars).release.yml— after the existing npm publish: syncserver.json's version topackage.json, installmcp-publisher,login http --domain pasteapp.io(using theMCP_REGISTRY_PRIVATE_KEYsecret, already set on this repo), andmcp-publisher publish.Auth
Domain (HTTP) auth for the
io.pasteappnamespace. The Ed25519 public-key proof is served from the site athttps://pasteapp.io/.well-known/mcp-registry-auth(companion PR:pasteapp/pasteapp.io#119). The private key lives only in the repo secret.Go-live order (important)
pasteapp.io#119so the well-known proof is live in production.@pasteapp/mcp@0.1.2to npm, then publishes the registry listing.Both domain validation (step 1) and package validation (the published 0.1.2 carrying
mcpName) must be satisfied beforemcp-publisher publishsucceeds.🤖 Generated with Claude Code