Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Settings keys

sdkMcpServerManifests

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

SDK MCP servers can now skip live handshakes by supplying a pre-captured manifest at initialization

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.265.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 161on this box, as of v2.1.322
Written about v2.1.265 first named in a changelog, 8 Sep 2026

In the changelogs

4

Releases whose published page names sdkMcpServerManifests.

  1. v2.1.286
    SDK startup now reports what happened to each in-process MCP server manifest

    Claude Code now records an outcome for each MCP server manifest the SDK sends at startup, and remote workers no longer use them

    found in this entry's text, named in this entry

  2. v2.1.281
    SDK can hand in-process MCP server manifests to the CLI at initialize

    The Agent SDK can now read tool lists from in-process MCP servers itself and pass them to the CLI when it starts

    found in this entry's text

  3. v2.1.265
    SDK MCP servers can now hand over a pre-captured manifest instead of handshaking live

    SDK MCP servers can now skip live handshakes by supplying a pre-captured manifest at initialization

    found in this entry's text, named in this entry

  4. v2.1.265
    SDK MCP servers can now skip the control-channel handshake via manifests

    SDK-registered in-process MCP servers can now skip a round-trip handshake at session start

    found in this entry's text, named in this entry

First cited

3

The earliest release whose published evidence quoted sdkMcpServerManifests was v2.1.265, 8 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.2658 Sep 2026sdkMcpServerManifests entry for '${Bt}' was not captured with MCP protocol ${xEe} - ignoring it; the server will handshake over the control channel
v2.1.28123 Sep 2026sdkMcpServerManifests
v2.1.28630 Sep 2026sdkMcpServerManifests not honoured on this remote-session worker

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback