{"version":"2.1.323","anchor":"cowork-only-gating-of-sdk-mcp-server-manifests","canonical_anchor":"cowork-only-gating-of-sdk-mcp-server-manifests","heading":"SDK MCP server manifests are described as Cowork-only on remote sessions","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/cowork-only-gating-of-sdk-mcp-server-manifests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### SDK MCP server manifests are described as Cowork-only on remote sessions\n\nClaude Code's description of `sdkMcpServerManifests` now says remote sessions use them only in interactive Cowork chats started from claude.ai\n\n**What**\n\n`sdkMcpServerManifests` is how the Agent SDK tells Claude Code about MCP servers when it starts. Claude Code's own description of this field has changed. It now says a manifest is reported as `not_honoured` when the remote session is not an interactive Cowork chat started from claude.ai.\n\nBefore, the description said manifests were not used when manifests, or remote manifests, were switched off in this copy of Claude Code. Only the description changed. The check Claude Code runs may not have changed.\n\n**Why**\n\nIf you build on the SDK, this describes a narrower set of remote sessions where manifests are used.\n\n- Area: SDK\n- Names: `sdkMcpServerManifests`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}