{"version":"2.1.286","anchor":"headless-mcp-control-sdk-server-enabledisable-and-register","canonical_anchor":"headless-mcp-control-sdk-server-enabledisable-and-register","heading":"SDK programs can switch off and back on the MCP servers they registered","tier":"use","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/headless-mcp-control-sdk-server-enabledisable-and-register","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### SDK programs can switch off and back on the MCP servers they registered\n\nPrograms driving Claude Code through the SDK can now disable and re-enable MCP servers they registered themselves\n\n**Unclear.** The exact name of the request an SDK program sends to do this is not known.\n\n**What**\n\nThe SDK is the kit for driving Claude Code from your own program. Such a program can register its own MCP servers. An MCP server is an add-on that gives Claude extra tools through the Model Context Protocol.\n\nWhen Claude Code runs without its interactive screen under such a program, the program can now disable an MCP server it registered and enable it again later.\n\n**Why**\n\nIf you build on the SDK, you can turn your own MCP servers off and on during a run without removing them.\n\n- Area: SDK\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}