{"version":"2.1.323","anchor":"sdk-mcp-servers-accept-dataflowserver-setting","canonical_anchor":"sdk-mcp-servers-accept-dataflowserver-setting","heading":"SDK programs can now set dataFlowServer when registering an MCP server","tier":"use","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sdk-mcp-servers-accept-dataflowserver-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### SDK programs can now set `dataFlowServer` when registering an MCP server\n\nPrograms driving Claude Code through the SDK can pass a new `dataFlowServer` setting for an MCP server, checked when it is registered\n\n**Unclear.** What `dataFlowServer` does is not stated.\n\n**What**\n\nThe SDK lets another program drive Claude Code, and MCP servers are add-ons that give Claude extra tools. When such a program registers an MCP server, it can now pass `dataFlowServer` alongside `timeout`, `disableAutoBackground`, `connectorId` and `autoModeVerdictTools`.\n\nLike those, it takes effect when the server is first registered. Claude Code checks the value at that point and reports an invalid value as ignored.\n\n**Why**\n\nSDK programs have one more setting they can pass for each MCP server. If a value is reported as ignored, Claude Code is not using it.\n\n- Area: SDK\n- Names: `dataFlowServer`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}