Skip to content

v0.6.3 — silence mcp-adapter 0.5.0 annotations deprecation

Choose a tag to compare

View all tags
@oxyc oxyc released this 31 Jul 15:22
v0.6.3
7c4b77b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Follow-up to v0.6.2 (#30), which moved uri/mimeType into meta.mcp for resource abilities but left annotations at the top level.

mcp-adapter 0.5.0 resolves resource meta through get_mcp_meta(), preferring meta.mcp.{key} and logging a deprecation on top-level fallback — so every WP-CLI run emitted four notices:

[WARNING] Ability meta key "annotations" is deprecated. Use "mcp.annotations" instead. | Context: {"ability":"gds/block-types-list","deprecated_key":"annotations"}

(gds/block-types-list, gds/site-map, gds/design-theme-json, gds/acf-fields — the four resource abilities. Tools use a different code path that does not deprecate top-level annotations.)

Changed

  • annotations is now mirrored into meta.mcp for BlockCatalogResource, SiteMapResource, ThemeJsonResource and AcfFieldsResource.

The top-level copy is retained deliberately — tools still read only $ability_meta['annotations'], on 0.5.0 and on trunk. Removing it would silently drop annotations from every tool ability.

Compatibility

No breaking changes. mcp-adapter v0.3.0 and v0.4.1 read only top-level annotations for resources, so the nested copy is inert there and behavior is unchanged. Nothing in the adapter or WP core validates unknown keys inside meta.mcp.

Full changelog: v0.6.2...v0.6.3

Assets 2
Loading