{"version":"2.1.287","anchor":"mcp-tool-success-clears-needs-auth-new-mcp-telemetry","canonical_anchor":"mcp-tool-success-clears-needs-auth-new-mcp-telemetry","heading":"An MCP server can leave the needs-sign-in state after a successful tool call","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/mcp-tool-success-clears-needs-auth-new-mcp-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### An MCP server can leave the needs-sign-in state after a successful tool call\n\nAfter an MCP tool call succeeds, Claude Code can clear that server's marker saying it needs you to sign in again\n\n**Unclear.** It is not clear under what condition the marker is cleared, since that step runs only when a check passes.\n\n**What**\n\nMCP (Model Context Protocol) is a standard way to connect outside tools to Claude Code through servers. Claude Code marks a server as needing sign-in when one of its tool calls fails for that reason.\n\nAfter a successful call to one of that server's tools, Claude Code can now remove the marker. Before, a server could be marked as needing sign-in, but nothing removed the marker. The usage data Claude Code records for each tool call also gains details about the MCP server involved.\n\n**Why**\n\nA server whose sign-in starts working again can come out of the needs-sign-in state on its own.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}