Skip to content

release: v0.4.1 — publish to the official MCP Registry#55

Merged
aryamthecodebreaker merged 1 commit into
mainfrom
feat/mcp-registry
Jul 16, 2026
Merged

release: v0.4.1 — publish to the official MCP Registry#55
aryamthecodebreaker merged 1 commit into
mainfrom
feat/mcp-registry

Conversation

@aryamthecodebreaker

Copy link
Copy Markdown
Owner

The MCP ecosystem's directories (PulseMCP explicitly, and others) now aggregate from the official MCP Registry rather than taking direct submissions — so this wires FixMap into it once, permanently:

  • server.json for io.github.aryamthecodebreaker/fixmap (npm package, stdio transport, npx @aryam/fixmap mcp)
  • publish.yml gains an mcp-publisher login github-oidc && publish step — non-interactive, authenticated by this repo's OIDC identity, version-guarded like the npm steps
  • @aryam/fixmap gets the mcpName field the registry uses for npm ownership validation → requires the 0.4.1 patch bump (core/cli/action bumped in lockstep)

After merge: dispatch Publish once → npm 0.4.1 + registry entry in one run.

🤖 Generated with Claude Code

Adds server.json (io.github.aryamthecodebreaker/fixmap) and an OIDC
mcp-publisher step to publish.yml, so every release lands in the
official MCP Registry — which feeds PulseMCP and the other directories
that aggregate from it. The registry validates npm ownership via the
new mcpName field in @aryam/fixmap's package.json, which requires this
0.4.1 patch release. Both npm and registry steps skip versions that
already exist, so re-runs stay green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@aryamthecodebreaker
aryamthecodebreaker merged commit 5d4fb2f into main Jul 16, 2026
2 checks passed
@aryamthecodebreaker
aryamthecodebreaker deleted the feat/mcp-registry branch July 16, 2026 15:09
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