{"version":"2.1.257","anchor":"new-mcp-connector-declaration-error-for-locally-configured-s","canonical_anchor":"new-mcp-connector-declaration-error-for-locally-configured-s","heading":"New MCP connector-declaration error for locally-configured servers","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-mcp-connector-declaration-error-for-locally-configured-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New MCP connector-declaration error for locally-configured servers\n\nNaming a locally-configured MCP server where a claude.ai connector is expected now gives a distinct host_unavailable error.\n\nPublishing or declaring capabilities now surfaces a distinct `host_unavailable` error when a name refers to a locally-configured MCP server rather than a claude.ai connector. The error explains that host-configured servers aren't available in that session and points to using the connector's display name instead, or clearing the `mcp` capability.\n\n- Area: MCP\n- Names: `host_unavailable`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}