Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code 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

Use it now New Features
JSON All of v2.1.281
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SDKArea: what it touches
New FeaturesKind: in v2.1.281,
What probably matters to youSection of the release
What

The Agent SDK lets programs drive Claude Code from code. MCP servers are add-ons that give Claude extra tools, and some of them run inside your own program ("in-process"). The SDK's Query class has a new step, captureSdkMcpServerManifests().

This step runs on the first initialize when captureSdkMcpManifests is set and SDK MCP servers exist. It asks each in-process server to start (initialize) and to list its tools (tools/list), all within a time limit. It then sends the results to the CLI inside the initialize request, in a new field sdkMcpServerManifests. That field sits next to sdkMcpServers and sdkMcpServerConfigs.

Servers that are not captured before the time limit fall back to the older handshake over the control channel, which is a back-and-forth exchange of messages. The result is logged to telemetry (usage data sent back) as sdk_mcp_manifest_capture, with one of these outcomes:

Why

The CLI can learn what tools your in-process servers offer without a separate exchange for each one. The capture is controlled by captureSdkMcpManifests, which depends on the environment variable CLAUDE_AGENT_SDK_DISABLE_MCP_MANIFESTS. Setting that variable turns the capture off.

See this entry in the whole of v2.1.281 →

Feedback