feat(publish): publish to the official MCP Registry on release#1585
Merged
yury-s merged 2 commits intomicrosoft:mainfrom May 1, 2026
Merged
feat(publish): publish to the official MCP Registry on release#1585yury-s merged 2 commits intomicrosoft:mainfrom
yury-s merged 2 commits intomicrosoft:mainfrom
Conversation
Adds server.json and a publish.yml job that runs mcp-publisher after the npm release. Auto-syncs server.json's version from package.json so future releases only need to bump package.json. Fixes microsoft#1477
pavelfeldman
approved these changes
Apr 30, 2026
- Drop the auto-sync step; require server.json to be bumped in lockstep with package.json. CI fails if they drift. - Run mcp-publisher from the working directory instead of /usr/local/bin (no sudo needed). - Correct server.json to 0.0.71 to match current package.json.
yury-s
added a commit
that referenced
this pull request
May 1, 2026
#1586) ## Summary - Expands the gate on `publish-mcp-release-registry` so it also runs on `workflow_dispatch`. Lets us retroactively publish a previously-released version (or rerun a failed publish) from the Actions tab without re-running the npm release. - Bumps `server.json` to `0.0.72` to match `package.json`. The validation step added in #1585 would otherwise fail the next release, since `mark v0.0.72` (#1584) landed before #1585 — `server.json` was committed at `0.0.71`. ## Mechanics The job still `needs: publish-mcp-release-npm` so on a real `release` event it correctly waits for npm to publish first. On `workflow_dispatch`, the npm job is skipped (its own `if` is `release`-only), and `if: always() && needs.*.result != 'failure'/'cancelled'` lets the registry job run anyway. ## Follow-up Once merged, this enables a manual one-shot of v0.0.72 to the registry via the Actions tab. Follow-up to #1585. Reference #1477
This was referenced May 2, 2026
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
2 participants
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.jsondeclaring the npm and OCI packages under theio.github.microsoft/playwright-mcpnamespace (already claimed viamcpNameinpackage.json).publish-mcp-release-registryjob topublish.ymlthat runs after the npm release, auto-syncsserver.json's version frompackage.json, and publishes viamcp-publisherusing GitHub OIDC (no PAT needed).registryOnlyMCP policies (e.g. VS Code + Copilot in security-hardened setups) by listing@playwright/mcpin the official registry.Fixes #1477
Precedent
microsoft/mcp-dotnet-samples publishes
io.github.microsoft/awesome-copilotto the registry from an hourly cron using the exact same flow (id-token: write+ curl-fetchedmcp-publisher+login github-oidc). It's been running successfully for weeks, so the GitHub-OIDC path is confirmed to work undermicrosoft/*corp policy — no DNS / Key Vault setup needed (unlike the reverted #1197 attempt that used thecom.microsoft/...namespace).Notes
server.json's committed version is just a placeholder; the workflow rewrites it frompackage.jsonbefore publish, so futurechore: mark vX.Y.Zcommits don't need to touchserver.json.