Tags

fix(mcp): Leave false defaults out of the MCP Registry manifest

The MCP Registry drops false booleans from a listing, so after #1986
spelled out isRequired: false and isSecret: false, the listing no longer
deep-equals server.json. Craft's mcp-registry target checks exactly that
after publishing, so the 0.49.0 publish failed there, and a retry fails
the same check against the existing listing.

Leave the fields out (false is their default) and add a server.json
check that keeps them out.

Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>

release: 0.48.0

release: 0.47.0

release: 0.46.0

release: 0.42.0

release: 0.41.0

release: 0.40.0

release: 0.39.0

release: 0.38.0

release: 0.37.0