Skip to content

ci: publish server.json to the MCP Registry on release tags - #8

Merged
tiltom merged 1 commit into
mainfrom
ci/mcp-registry-publish
Nov 10, 2026
Merged

tiltom merged 1 commit into
mainfrom
ci/mcp-registry-publish

Conversation

@tiltom

@tiltom tiltom commented Nov 9, 2026

Copy link
Copy Markdown
Member

Why

The MCP Registry listing for io.github.flagrix-io/flagrix is still at 0.1.0 (published 2026-07-08), while npm is at 0.5.0. Nothing has published server.json since the first release. The interactive mcp-publisher login github also can't publish under an organisation namespace any more (modelcontextprotocol/registry#1468). The registry docs recommend logging in from GitHub Actions with OIDC instead.

What

.github/workflows/release.yml (still triggered by v* tags):

  1. New first step: check versions match the tag. The job fails before anything is published if the tag differs from package.json version, server.json version or server.json packages[0].version. Otherwise npm could get one version while the registry advertises another.
  2. npm publish, unchanged.
  3. MCP Registry steps, after npm, because the registry only stores metadata pointing at the npm package. These follow the registry's GitHub Actions guide:
    • install cosign (pinned by commit SHA, as in the guide)
    • download mcp-publisher pinned to v1.8.4 and verify its Sigstore bundle before extracting it. v1.8.8 is the newest release but came out 3 days ago, so it isn't pinned yet.
    • mcp-publisher login github-oidc: no secret needed; it uses the job's existing id-token: write permission
    • mcp-publisher publish

server.json moves from the deprecated 2025-09-29 schema to 2025-12-11. The only change in that schema is for remote servers, so for an npm package the migration is just the URL.

Checked

  • mcp-publisher validate on the new server.json: valid, with no deprecation warning (before: valid, with a deprecation warning).
  • The workflow YAML parses, and the steps are in the order listed above.
  • I ran the version-check step locally: v0.5.0 passes; v0.5.1 (against 0.5.0 files) fails with the mismatch error.
  • Not run: the cosign verification and the OIDC login/publish. They only run on a real tag, so the first real test is the next release.

After merging

  • 0.5.0 isn't published by this PR. Its tag already ran. Publish it once by hand from main, using a GitHub token with read:org from an org owner: mcp-publisher login github --token … then mcp-publisher publish.
  • From the next tag on, each release updates npm and the registry together. Releasing means bumping package.json and both server.json versions, otherwise step 1 fails.

The registry listing (io.github.flagrix-io/flagrix) was still at 0.1.0:
nothing published server.json after the first release, and the
interactive `mcp-publisher login github` can no longer publish to an
organisation namespace (modelcontextprotocol/registry#1468).

The release workflow now, after `npm publish`:
- installs mcp-publisher at a pinned version (v1.8.4) and verifies its
  Sigstore bundle with cosign before running it
- logs in with `mcp-publisher login github-oidc` (no secret; uses the
  job's existing id-token: write permission)
- runs `mcp-publisher publish`

A first step fails the job before anything is published if the tag
disagrees with package.json or either version in server.json.

server.json moves to the current 2025-12-11 schema; the 2025-09-29 one
is deprecated. For an npm package the migration is only the URL.
@tiltom tiltom self-assigned this Nov 10, 2026
@tiltom
tiltom merged commit a069c69 into main Nov 10, 2026
3 checks passed
@tiltom
tiltom deleted the ci/mcp-registry-publish branch November 18, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant