Fix: register MCP resource URI under meta.mcp.uri

[oxyc]

Problem

Kinsta production logs (site medihealth, ~448 errors/day) show:

[ERROR] ... Resource URI not found in ability meta for 'gds/block-types-list'

(also gds/site-map, gds/design-theme-json, gds/acf-fields), emitted by WP\MCP\Domain\Resources\RegisterAbilityAsMcpResource in the WordPress/mcp-adapter dependency.

Root cause

The four MCP resource abilities declared their uri and mimeType at the top level of meta. As of WordPress/mcp-adapter 0.5.0, the adapter resolves the resource URI from meta.mcp.uri (the canonical location); top-level meta.uri / meta.mimeType are deprecated. When mcp.uri is absent the adapter returns a resource_uri_not_found WP_Error, which is what flooded the logs.

The adapter's lookup (for reference):

// RegisterAbilityAsMcpResource::get_uri()
$uri = $this->get_mcp_meta( 'uri', 'string' ); // reads mcp.uri first
if ( null === $uri ) {
    return new WP_Error( 'resource_uri_not_found',
        "Resource URI not found in ability meta for '%s'. URI must be provided at 'mcp.uri'." );
}

Fix

• Move uri and mimeType into meta.mcp for all four resource abilities (BlockCatalogResource, SiteMapResource, ThemeJsonResource, AcfFieldsResource). This is the canonical, non-deprecated location and resolves both the error and the _doing_it_wrong deprecation notices.
• Update HelpAbility to read meta.mcp.uri with a top-level fallback so the help index (and HelpAbilityTest::test_resources_include_uri) keeps working.
• annotations is intentionally left at the top level because SchemaValidationTest::test_all_abilities_have_annotations asserts on meta.annotations.

Verification

• php -l clean on all changed files
• composer lint (Pint) — passed
• composer stan (PHPStan, level per repo config) — no errors
• Full PHPUnit suite requires the wp-env DB harness (not runnable in this environment)

🤖 Generated with Claude Code