Skip to content

fix(registry): list the bridge under com.sourcey/sourcey - #10

Open
auscaster wants to merge 1 commit into
mainfrom
chore/com-sourcey-namespace
Open

auscaster wants to merge 1 commit into
mainfrom
chore/com-sourcey-namespace

Conversation

@auscaster

Copy link
Copy Markdown
Member

Summary

  • Binds @sourcey/mcp-server to Sourcey's hosted registry record com.sourcey/sourcey through mcpName. This replaces the separate GitHub-owned io.github.sourcey/mcp-server entry, so Sourcey has one Registry entry under its own domain, listing the hosted endpoint and this package as the local stdio alternative.
  • Removes this repository's own registry publishing (server.json, .github/workflows/publish-mcp-registry.yml, scripts/verify-registry.mjs). Sourcey's hosted MCP release lists the package instead.
  • Bumps the bridge to 1.0.1. scripts/metadata.mjs now rejects any record name other than com.sourcey/sourcey.
  • The test harness reads the expected handshake version from package.json instead of a hard-coded 1.0.0.

No bridge runtime or tool behaviour changes.

Release order

  1. Merge, then tag v1.0.1. release.yml publishes npm 1.0.1 with mcpName: com.sourcey/sourcey; no registry step runs from this repo any more.
  2. Sourcey's hosted MCP 1.3.16 publishes com.sourcey/sourcey listing @sourcey/mcp-server@1.0.1. The Registry checks the npm package's mcpName, so step 1 has to land first.
  3. Deprecate every io.github.sourcey/mcp-server version with a pointer to com.sourcey/sourcey.

The tag triggers the npm release, so don't tag until this is reviewed and merged.

Verification

  • npm run verify passes locally: clean build, metadata generation and check, Biome, 3/3 tests, and the packed-tarball install check at 1.0.1.

The bridge was listed in the official MCP Registry as the GitHub-owned
io.github.sourcey/mcp-server. Sourcey's listings carry its own domain, and
one Sourcey entry is cleaner than two, so the package now binds to the
hosted record com.sourcey/sourcey as its local stdio alternative.

- mcpName and the distribution registry_name are com.sourcey/sourcey, and
  the metadata check rejects any other record.
- This repository no longer publishes a registry record of its own:
  server.json, the registry publish workflow and its readback script are
  removed. Sourcey's hosted release lists the package.
- Version 1.0.1. The registry admits the package only when the exact npm
  version it lists carries the new mcpName.
- The test harness reads the expected handshake version from package.json.

This branch has not been deployed

No deployments
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