Automate MCP Registry publish and tag package as McpServer#106
Merged
Conversation
Add McpServer package type alongside DotnetTool so the package surfaces under nuget.org's "MCP Server" filter; the tool install path is unchanged. Move server.json to .mcp/server.json and rewrite the release workflow to publish to NuGet via Trusted Publishing (OIDC) and then publish the listing to the Official MCP Registry, replacing the manual mcp-publisher step. Co-Authored-By: Claude Opus 4.8 <[email protected]>
This was referenced Jun 25, 2026
Merged
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
1 participant
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.
Brings TokenSaver's release pipeline to parity with the McpOrchestrator setup: the package is now tagged as an MCP server, and the Official MCP Registry listing publishes automatically on a tag instead of by hand.
Changes
McpServerpackage type added alongsideDotnetToolinmcp/TokenSaver.Mcp.csproj. Verified by packing — both types land in the nuspec, sodnx/dotnet toolinstall is unaffected while the package now surfaces under nuget.org's "MCP Server" package-type filter.server.jsonmoved to.mcp/server.json(tracked as a rename).release.ymlrewritten:mcp-registryjob stamps the tag version into.mcp/server.json, waits for the NuGet README to go live, then authenticates viagithub-oidcand publishes the listing. Replaces the manualmcp-publisher publishstep.PUBLISH_NUGET/PUBLISH_MCP_REGISTRYrepo variables.CONTRIBUTING.mdupdated for the new path and automated registry publish.Required repo configuration (already set up)
Byggarepop, repoTokenSaver, workflowrelease.yml, environmentrelease)NUGET_USERsecretPUBLISH_NUGET=trueandPUBLISH_MCP_REGISTRY=truerepo variables