{"version":"2.1.260","anchor":"mcp-server-manifest-resolution-local-servers-can-now-satisf","canonical_anchor":"mcp-server-manifest-resolution-local-servers-can-now-satisf","heading":"MCP server manifest resolution: local servers can now satisfy first-party host references","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/mcp-server-manifest-resolution-local-servers-can-now-satisf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### MCP server manifest resolution: local servers can now satisfy first-party host references\n\nLocal MCP servers can now satisfy manifest references to first-party hosts by name match.\n\nWhen resolving a capability manifest's MCP server entries against a first-party host id, the resolver now also checks whether a locally-configured server's name (or its normalized form) matches that host. If it does, the manifest entry is treated as referring to that local server (`local_server_as_first_party`) instead of being flagged as unresolved or opaque.\n\n- Area: MCP\n- Names: `local_server_as_first_party`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}