docs: state field length limits in the publishing quickstart - #1526
Open
beeswaxpat wants to merge 1 commit into
Open
docs: state field length limits in the publishing quickstart#1526beeswaxpat wants to merge 1 commit into
beeswaxpat wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Fable 5 <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.
The server.json schema enforces length limits on free-form fields (in the 2025-12-11 schema:
descriptionandtitle100 characters,name200, version strings 255), but none of the user-facing docs state them; about.mdx only mentions "strict character limits" without numbers. Hitting thedescriptionlimit is a common first-publish failure:mcp-publisher initgenerates the field, the publisher writes a sentence or two, and publish/validate fails with a schema error that has to be traced back to the length. #1184 asks for exactly this documentation.This adds one note to the quickstart at the point where the publisher first edits
server.json, so the limits are visible before the first publish attempt. Complements #1267, which improves the validator's error message for the same failure.🤖 Generated with Claude Code