Repository navigation
Conversation
Each server gets a `server.json`, its entry for the official MCP Registry. The committed file carries no version: `scripts/mcp-registry-entries.mjs` stamps it from the package manifest on the released commit, after checking the entry against the package it points at (`mcpName`, or the README's `mcp-name:` marker), so a version still lives only in the manifests. `release.yml` gains `publish-mcp-registry`, which runs after the package publish jobs, in the `release` environment, and registers each entry the registry does not already list with `mcp-publisher login github-oidc`. The publisher binary is pinned by release and SHA-256. The job has no checkout and runs no action; what it registers reaches it as a `detect-packages` output. Nothing is registered by this change: the first entries are published by the next Release a maintainer publishes and approves. Closes #3047 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: cliffhall <cliff@futurescale.com>
|
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 16 | 0 | 0 | 1 |
| Head | 16 | 0 | 0 | 1 |
Updated by this run for 3c42f9fe3b146fe2fd8879bae203176ff18d9866.
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 1 | 0 | 0 | 0 |
| Head | 1 | 0 | 0 | 0 |
Updated by this run for 3c42f9fe3b146fe2fd8879bae203176ff18d9866.
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 22 | 4 | 8 | 5 |
| Head | 22 | 4 | 8 | 5 |
Updated by this run for 3c42f9fe3b146fe2fd8879bae203176ff18d9866.
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 1 | 1 | 0 | 0 |
| Head | 1 | 1 | 0 | 0 |
Updated by this run for 3c42f9fe3b146fe2fd8879bae203176ff18d9866.
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 14 | 2 | 0 | 0 |
| Head | 14 | 2 | 0 | 0 |
Updated by this run for 3c42f9fe3b146fe2fd8879bae203176ff18d9866.
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 9 | 0 | 1 | 0 |
| Head | 9 | 0 | 1 | 0 |
Updated by this run for 3c42f9fe3b146fe2fd8879bae203176ff18d9866.
|
| Tools | Prompts | Resources | Resource templates | |
|---|---|---|---|---|
| Base | 3 | 0 | 0 | 0 |
| Head | 3 | 0 | 0 | 0 |
Updated by this run for 3c42f9fe3b146fe2fd8879bae203176ff18d9866.
There was a problem hiding this comment.
🟡 Changes recommended
The filesystem registry entry lacks a required, repeatable allowed-directory argument, causing generated launches to use an empty allow-list that breaks tool calls and prevents legacy clients without Roots from initializing.
1 open issue
What changed in this PR
Adds release-time registration of the seven reference servers in the official MCP Registry, addressing the repository-owned portion of #3047. Merging alone registers nothing; registration follows package publication during a maintainer-approved release.
Changes:
- Adds versionless registry entries, validated against package metadata and stamped from manifest versions.
- Adds an OIDC-authenticated publishing job that skips existing entries and reports individual failures.
- Adds validation and workflow regression tests, plus release and maintenance documentation.
| File | Description |
|---|---|
src/time/server.json |
Declares the Time registry entry. |
src/sequentialthinking/server.json |
Declares the Sequential Thinking registry entry. |
src/memory/server.json |
Declares the Memory registry entry. |
src/git/server.json |
Declares the Git registry entry. |
src/filesystem/server.json |
Declares the Filesystem registry entry. |
src/fetch/server.json |
Declares the Fetch registry entry. |
src/everything/server.json |
Declares the Everything registry entry. |
scripts/release-mcp-registry.test.mjs |
Tests publishing decisions and workflow safeguards. |
scripts/mcp-registry-entries.test.mjs |
Tests entry validation and version stamping. |
scripts/mcp-registry-entries.mjs |
Validates and stamps entries for release. |
RELEASING.md |
Documents registration, approvals, and recovery. |
AGENTS.md |
Records registry metadata maintenance rules. |
.github/workflows/release.yml |
Passes stamped entries to the registry publishing job. |
.claude/skills/release/SKILL.md |
Adds approval and registration verification steps. |
.claude/skills/project-structure/SKILL.md |
Documents registry files in server layouts. |
Review effort: Balanced
…try entry A client that builds its launch command from the entry had no directory input to collect, so the server would start with an empty allow-list. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: cliffhall <cliff@futurescale.com>
|
Copilot round 1: one finding, fixed.
|
|
Copilot round 2: clean (no findings; the round 1 finding is marked resolved). The review loop ends here on the first clean round. Not merged: merging is the maintainer's. |

Closes #3047
Description
Adds what this repository needs to list its seven servers in the official MCP Registry. Merging this registers nothing. The first entries are published by the next GitHub Release a maintainer publishes and approves.
src/<server>/server.json(seven files): each server's registry entry, namedio.github.modelcontextprotocol/server-<name>, the name every published package already claims (mcpNameinpackage.json, themcp-name:marker in the Python READMEs). The committed file carries no version.scripts/mcp-registry-entries.mjs: checks each entry against the package it points at (name equals the package's marker, identifier equals the manifest's name, description within the registry's 100 characters, one stdio package, no committed version) and stamps the version frompackage.json/pyproject.toml. A version still lives only in the manifests, so the Version Packages and Prepare Python Release PRs are unchanged. The check also runs in the script tests (validate:guards), so a bad entry fails CI on the PR that introduces it, not at release time.release.yml:detect-packagesruns the script and hands the stamped entries on as a job output (mcp_registry), the way it already hands on each package's expected name and version.publish-mcp-registry, runs afterpublish-npmandpublish-pypi(the registry accepts an entry only for a package version that is already on npm or PyPI). For each entry it asks the registry's public API whether that version is listed: 200 skips it, 404 queues it, anything else fails that entry. If anything is queued it runsmcp-publisher login github-oidconce and publishes each.RELEASING.md(a new The MCP Registry section, the job table, the release steps),AGENTS.md(the tree, and a rule under Versions), and thereleaseandproject-structureskills.How the new job meets the credentialed-job rules
verify:action-pinspasses, anddetect-packages, whose output it reads, was already pinnedmcp-publisher, pinned to releasev1.8.9and to the SHA-256 of that release's Linux archive, checked before it is unpackedrelease: publishedrun, and it takes thereleaseenvironment, so it waits for a required reviewer like the other publish jobsdetect-packagesjob output, computed on the released commit before any dependency code runs. The job re-checks each directory, name and version before using them in a path or URLThere is no secret and no account: the registry grants
io.github.modelcontextprotocol/*to an OIDC token whoserepository_owneris this organization.Server Details
None (repository-wide). No server's code, tools, resources or prompts change. Each server gains a
server.jsonbeside its manifest; the npm packages do not ship it (filesis["dist"]), and the Python sdists gain one small metadata file.Motivation and Context
#3047 asks for the reference servers to be listed in the registry. The package-side markers shipped long ago, and nothing else existed: no
server.json, no publish step. None of the seven is listed today (see the probes).The issue's own plan,
mcp-publisher login githubfrom a maintainer's machine, no longer works for this namespace. The registry's authentication docs now say the interactive login cannot publish to an organization namespace at all, and name two ways that can: GitHub Actions OIDC, or an organization Owner's personal access token. This PR takes the first, which needs no token.Not in this PR
https://modelcontextprotocol.io/mcp), the eighth item in the issue. This repository has none of it: it is served by the documentation site, whose source ismodelcontextprotocol/modelcontextprotocol(docs/). Its entry is aremotesentry with no package to verify, and it belongs with that repository.mcp/<server>), which the issue mentions as a possibility. The registry verifies an image by a label inside it, and these images are not built by this repository's workflows.How Has This Been Tested?
No client-observable surface, so targeted probes. Nothing below authenticated to the registry or published to it.
1. None of the seven is registered today (the registry's public API, by name):
2. Every current package version carries the marker the registry verifies:
3. The stamped entries validate against the registry's published schema (
https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json, with Ajv), and the committed, version-less file does not, which is why the stamp exists:4. The guard fires on a planted defect, then passes. With
src/git/server.jsongiven a different name and identifier and a committed version:Restored: exit 0.
5. The job's own shell, run from the workflow file with
curlandmcp-publisherstubbed (scripts/release-mcp-registry.test.mjs, 25 tests): every missing entry is published after one login; a listed version is skipped; with nothing missing no token is requested; a 500, 429, 302 or no answer fails that entry without publishing it and without stopping the others; one refused entry does not stop the rest and fails the job; an empty, malformed or out-of-namespace job output registers nothing.scripts/mcp-registry-entries.test.mjs(40 tests) covers the entry rules, the stamp, the README marker, and the repository's own entries.6.
npm run local:gate: exit 0.Not exercised, and cannot be before a Release: the live
login github-oidcandpublishcalls. The job is written so a failure there cannot affect the packages, which are already published when it starts.mcp-publisher validatewas not run locally either; probe 3 is the schema check it would have made.Breaking Changes
None. No client configuration changes.
Types of changes
Checklist
modelcontextprotocol/registrydocs/)RELEASING.mdandAGENTS.mdare updated)npm run changeset) if this changes what a TypeScript server publishes (not applicable:server.jsonis outside each package'sfiles, so no published TypeScript package changes)MCP_PUBLISHER_*pins, in the workflow andRELEASING.md)Additional context
What a maintainer does after merging
releaseskill gains (step 6), or by searching the registry forio.github.modelcontextprotocol.Choices a maintainer may want to revisit
releaseenvironment on the new job. The registry does not bind to it; it is there so registering waits for a person. The cost is a second approval moment per release. Droppingenvironment: releasefrom the job would let it follow the approved package publishes on its own.🤖 Generated with Claude Code