{"version":"2.1.275","anchor":"claudeai-mcp-connector-listing-now-includes-additional-ins","canonical_anchor":"claudeai-mcp-connector-listing-now-includes-additional-ins","heading":"claude.ai MCP server fetch now includes additional installs, with fallback","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/claudeai-mcp-connector-listing-now-includes-additional-ins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### claude.ai MCP server fetch now includes additional installs, with fallback\n\nClaude Code now fetches 'additional install' MCP servers from claude.ai and falls back gracefully if that request is refused\n\n**What**\n\nThe fetch of MCP (Model Context Protocol) servers hosted on claude.ai now requests `include_additional_installs=true`. Entries flagged as an additional install are collected separately, sorted by creation time, and appended after the primary de-duplicated list. If the extended request fails with certain errors, Claude Code retries once against the plain endpoint (without additional installs) without using up a full attempt from the normal retry budget, and logs a telemetry reason for the fallback.\n\n**Why**\n\nThis surfaces MCP servers that were installed as extras and weren't previously shown, while keeping server fetching resilient if the new request parameter isn't supported.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}