{"version":"2.1.299","anchor":"mcp-servers-using-claude-codes-reserved-address-are-refused","canonical_anchor":"mcp-servers-using-claude-codes-reserved-address-are-refused","heading":"MCP servers at an address Claude Code reserves are refused with an explanation","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-servers-using-claude-codes-reserved-address-are-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP servers at an address Claude Code reserves are refused with an explanation\n\nClaude Code now refuses MCP servers at an address it reserves for itself and tells Claude that retrying will not help\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Claude Code now refuses a configured MCP server whose address it reserves for its own use, and reports this as a third kind of MCP failure, next to connection failures and servers blocked by managed policy.\n\n- The refusal reason is `reserved_address`, with the message \"MCP server refused by Claude Code, which reserves its address\".\n\n- Claude is told that these servers are refused because Claude Code reserves their address, that retrying will not help, and that whoever added the entry can remove it or change its address.\n\n- A tool from such a server tells Claude the tool is unavailable.\n\n- ToolSearch gives the same note when it finds no match.\n\nBefore, failed servers were split only into policy-blocked servers and other connection failures.\n\n**Why**\n\nIf one of your MCP entries clashes with an address Claude Code uses itself, you get an accurate explanation instead of a plain connection failure that Claude may keep retrying.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}