Repository navigation
Add empty tools[] to manifest.json and bump to 0.1.2 to enable Smithery publish - #15
Merged
Merged
Conversation
…ry publish - The Smithery CLI's getBundleDeployPayload (smithery-ai/cli src/lib/mcpb.ts) only includes serverCard.tools when manifest.tools is truthy; omitting tools from the manifest results in a serverCard with only serverInfo set, which the Smithery server rejects with 400 "No values to set" - Adding tools: [] to mcp/manifest.json makes the validator treat the bundle as having "something to set" and the deployment succeeds (verified with a local pack + smithery mcp publish round-trip: release cecabc00 accepted with status SUCCESS) - Workaround for arcadeai-labs/smithery-cli#770; arcadeai-labs/smithery-cli#787 is the opposite failure mode (non-empty tools[] is rejected because MCPB tools schema differs from registry Tool schema), so an empty array is currently the only path that works - mcp/{package.json,package-lock.json,manifest.json,server.json} bumped to 0.1.2 in sync via npm version --no-git-tag-version plus manual edits Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Summary
Bump
@dominion525/familiar-mcpto0.1.2and addtools: [](empty array) tomcp/manifest.jsonso the bundle can be published to Smithery without hitting their server-side400 {"error":"No values to set"}.Why
The Smithery CLI's
getBundleDeployPayloadonly includesserverCard.toolswhenmanifest.toolsis truthy. If the manifest omitstools, the payload'sserverCardends up with onlyserverInfoset, and the Smithery server rejects it with#770.Adding an empty
tools: []makes the Smithery validator treat the bundle as having "something to set", and the deployment goes through. Verified with a local pack +smithery mcp publishround-trip:Release cecabc00-... accepted, status: SUCCESS.Note:
#787is the opposite failure mode — a non-emptytools[]is rejected because the MCPB tools schema doesn't match the registry Tool schema. So an emptytools[]is currently the only path that lets a stdio.mcpbbundle through Smithery's ingestion.Changes
mcp/manifest.json— adds"tools": []mcp/{package.json,package-lock.json,manifest.json,server.json}— bumped to0.1.2in sync