{"version":"2.1.314","anchor":"ccr-mcp-ticket-header-x-ccr-ticket-mcp-cached-and-replayed","canonical_anchor":"ccr-mcp-ticket-header-x-ccr-ticket-mcp-cached-and-replayed","heading":"MCP connections in CCR sessions now keep and resend a server ticket","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/ccr-mcp-ticket-header-x-ccr-ticket-mcp-cached-and-replayed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### MCP connections in CCR sessions now keep and resend a server ticket\n\nClaude Code stores a ticket the server sends in an MCP response header and resends it on later requests while it stays valid\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside tools and services. When a server answers an MCP request with the `x-ccr-ticket-mcp` header, Claude Code now saves that ticket along with the login details it arrived with. It adds the ticket to later requests only while the same login details are in use and the ticket has not expired. If the server sends the header empty, the saved ticket is cleared.\n\n**Why**\n\nThis lets the server keep track of state for MCP calls that go through CCR.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}