1.15.4: pack .mcp/server.json into the package#108
Merged
Conversation
Tagging the package as McpServer in 1.15.3 was not enough for nuget.org to generate the VS Code MCP config — the manifest must ship inside the .nupkg. Pack the repo-root .mcp/server.json into the package's .mcp/ folder. Co-Authored-By: Claude Opus 4.8 <[email protected]>
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.
Follow-up to #106/#107. nuget.org reported it could not generate the VS Code MCP server config for 1.15.3 because the package did not embed
.mcp/server.json— tagging theMcpServerpackage type alone is not sufficient; the manifest must ship inside the.nupkg.Change
mcp/TokenSaver.Mcp.csproj: pack the repo-root.mcp/server.jsoninto the package's.mcp/folder (PackagePath="\.mcp\"). Verified by packing — the.nupkgnow contains.mcp/server.json.The committed manifest is the same file the release workflow re-stamps to the tag version before publishing the registry listing, so the packed and registry versions stay in sync.