chore: shorten description ≤100 chars + bump v0.2.3 — fix MCP registry publish#11
Merged
Merged
Conversation
…y publish v0.2.2 published successfully to PyPI (m-dev-tools-mcp 0.2.2 live) but the MCP registry rejected the server.json with HTTP 422: validation failed: expected length <= 100 body.description: "MCP server for the m-dev-tools org catalog — exposes route_intent, describe, and verify as first-class agent tools." (116 chars) The official registry caps `description` at 100 characters; ours was 116. Easy fix: shorten to a 76-char form that keeps the same gist. Description rewritten everywhere it appears: * server.json description: now 76 chars * pyproject.toml description: same, kept in sync (no length limit on PyPI side, but the two should match — registry consumers read both) Bump to v0.2.3 (PyPI 0.2.2 is live + immutable): * pyproject.toml: version 0.2.2 → 0.2.3 * src/m_dev_tools_mcp/__init__.py: __version__ → "0.2.3" * server.json: top-level version + packages[0].version → "0.2.3" * dist/mcp-tools.json regen Also lands the belt-and-suspenders cleanup line in Makefile's clean target that didn't make it into PR #10 — adds `rm -f dist/*.whl dist/*.tar.gz` so a forgotten `python -m build` without --outdir doesn't leak through to a future PyPI upload. ### Verified locally * make check — ruff + mypy + 41/41 pytest + manifest + check-agents drift gates all clean * make build → wheel-out/m_dev_tools_mcp-0.2.3-py3-none-any.whl * description-length sanity: server.json description is 76 chars (well under the 100-char registry cap) ### After merge Push v0.2.3 tag. release.yml fires; expected: 4-of-4 steps pass (build / GH-Release / PyPI / MCP registry), m-dev-tools-mcp 0.2.3 live on both PyPI and registry.modelcontextprotocol.io.
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.
Summary
v0.2.2 published successfully to PyPI (
m-dev-tools-mcp0.2.2 is live), but the MCP registry rejected theserver.jsonwith HTTP 422:The official registry caps
descriptionat 100 characters. This PR shortens it to 76 chars (well under the cap), bumps to v0.2.3 (PyPI 0.2.2 is immutable), and folds in the belt-and-suspenders Makefile cleanup that didn't make it into PR #10.Changes
server.json+pyproject.tomldescription: shortened to"MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify."(76 chars; same gist as before). Kept in sync between the two files.pyproject.toml,__init__.py,server.json,dist/mcp-tools.jsonregen.Makefileclean: addsrm -f dist/*.whl dist/*.tar.gzfor the case wherepython -m buildis invoked without--outdirand writes wheels underdist/. Defensive — the wheel-out shift in PR chore: build wheel to wheel-out/ + bump to v0.2.2 — fix Phase-6 publish #10 already prevents this for normal runs.Verified locally
make checkclean — ruff + mypy + 41/41 pytest + manifest + check-agents drift gatesmake build→wheel-out/m_dev_tools_mcp-0.2.3-py3-none-any.whlStep status from v0.2.2's run
Test plan
wheel-out/v0.2.3tag → release.yml fires end-to-end → all four publish steps succeed → m-dev-tools-mcp 0.2.3 live on PyPI and the MCP registry underio.github.m-dev-tools/m-dev-tools-mcp.