{"version":"2.1.280","anchor":"mcp-server-removal-now-also-clears-the-auth-cache-entry","canonical_anchor":"mcp-server-removal-now-also-clears-the-auth-cache-entry","heading":"MCP server removal now also clears the auth-cache entry","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mcp-server-removal-now-also-clears-the-auth-cache-entry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP server removal now also clears the auth-cache entry\n\nRemoving an MCP server now also clears its cached OAuth authentication entry\n\n**What**\n\nRunning `mcp remove` to remove an MCP (Model Context Protocol) server now also clears that server's entry from the authentication cache, via a new `removeMcpAuthCacheEntry` step, before the existing token and config cleanup runs.\n\n**Why**\n\nPreviously a removed server's cached OAuth credentials could linger behind. Clearing the cache entry on removal avoids a stale authentication record hanging around after the server itself is gone.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}