{"version":"2.1.300","anchor":"mcp-server-enabledisable-gets-idempotent-request-ids-listi","canonical_anchor":"mcp-server-enabledisable-gets-idempotent-request-ids-listi","heading":"Turning MCP servers on and off is safe to retry","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/mcp-server-enabledisable-gets-idempotent-request-ids-listi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Turning MCP servers on and off is safe to retry\n\nEnabling or disabling an MCP server can now carry a request id so a repeated request returns the earlier result instead of switching again\n\n**What**\n\nAn MCP server is an add-on that gives Claude extra tools. The request that turns one on or off can now carry an optional request id of up to 64 characters. Sending the same request again returns the earlier result instead of switching the server a second time.\n\nOther changes:\n\n- A disabled server is marked as disabled in the current server list\n\n- Listing servers now waits for any listing already in progress\n\n- Listing can wait a set time and can be limited to certain servers\n\n**Why**\n\nA request repeated by a remote caller, for example after a network hiccup, no longer applies twice, and the server list reflects the settled state.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}