{"version":"2.1.275","anchor":"mcp-client-connections-now-record-first-party-bearer-tokens","canonical_anchor":"mcp-client-connections-now-record-first-party-bearer-tokens","heading":"MCP client connections now record first-party bearer tokens","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/mcp-client-connections-now-record-first-party-bearer-tokens","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### MCP client connections now record first-party bearer tokens\n\nMCP connections now store first-party bearer tokens separately in memory\n\n**What**\n\nWhen Claude Code successfully connects to an MCP (Model Context Protocol, a way for Claude to talk to external tools and data sources) server, it now also stores the first-party bearer authentication token for that connection in a new internal lookup table, alongside the existing table of auth providers.\n\n**Why**\n\nThis lets Claude Code track and reuse first-party bearer credentials per connection separately from general auth provider state, which is bookkeeping that supports more reliable authenticated MCP connections.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}