{"version":"2.1.295","anchor":"mcp-pagination-stops-on-a-repeated-cursor-transient-error-d","canonical_anchor":"mcp-pagination-stops-on-a-repeated-cursor-transient-error-d","heading":"MCP server lists can no longer loop forever, and fewer errors are retried","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-pagination-stops-on-a-repeated-cursor-transient-error-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### MCP server lists can no longer loop forever, and fewer errors are retried\n\nClaude Code stops reading an MCP server's list if the server repeats a page marker, and no longer treats HTTP status errors as temporary\n\n**What**\n\nMCP (Model Context Protocol) servers are add-on services that give Claude Code extra tools and data. They often send long lists one page at a time. Each page includes a marker that says where the next page starts.\n\n- Claude Code now remembers every page marker it has sent while reading a list. If the server sends one it has already seen, Claude Code stops reading. It logs the warning \"returned a nextCursor already sent in this walk\". Before, only a fixed page limit stopped it.\n\n- Connection errors are now judged temporary, and worth retrying, only for network problems such as a reset or closed connection, or for the message patterns already recognised. An error that carries an HTTP status or code from 100 to 599, or a negative number, is no longer treated as temporary.\n\n- In sessions that prepare no output formats for MCP tools, Claude Code now accepts tool output without checking its format.\n\n**Why**\n\nA misbehaving MCP server can no longer keep Claude Code reading the same pages over and over. Errors that will not fix themselves, such as an HTTP error response, are no longer retried for nothing.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}