{"version":"2.1.323","anchor":"sdk-mcp-server-config-gains-dataflowserver-origin-oauth-ref","canonical_anchor":"sdk-mcp-server-config-gains-dataflowserver-origin-oauth-ref","heading":"SDK token refresh requests now say why, and server records note where a server came from","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sdk-mcp-server-config-gains-dataflowserver-origin-oauth-ref","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### SDK token refresh requests now say why, and server records note where a server came from\n\nAgent SDK token refresh requests now carry a reason, and MCP server records can note whether a server came from Anthropic, claude.ai or the user\n\n**What**\n\nThe Agent SDK is the toolkit that lets other programs, such as desktop apps, run Claude Code. Three of its message formats change:\n\n- MCP server settings (for add-ons that give Claude extra tools) gain an internal field recording where the host got the server: Anthropic, a claude.ai connector, or the user's own setup.\n\n- The request to refresh a sign-in token gains a field saying whether the token was refused or not.\n\n- The request asking the host app to refresh its own sign-in token gains a status of 401 or 403, the two usual web codes for a rejected sign-in.\n\n**Why**\n\nApps built on Claude Code, such as Desktop and Cowork, can tell why a token was asked for and where an MCP server came from.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}