{"version":"2.1.267","anchor":"ide-mcp-server-identified-via-x-mcp-server-id-header-and-fix","canonical_anchor":"ide-mcp-server-identified-via-x-mcp-server-id-header-and-fix","heading":"IDE MCP server identified via x-mcp-server-id header and fixed UUID","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/ide-mcp-server-identified-via-x-mcp-server-id-header-and-fix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### IDE MCP server identified via x-mcp-server-id header and fixed UUID\n\nClaude Code now recognizes its own IDE MCP server via a header and fixed ID, driving tool auto-allow\n\n**What**\n\nClaude Code can now tell when an MCP (Model Context Protocol) server connection is actually its own IDE integration by reading an `x-mcp-server-id` header from the server's configuration and comparing it against a fixed, known value. This recognition feeds into decisions like automatically allowing the `mcp__ide__executeCode` tool and detecting servers that are set up dynamically.\n\n**Why**\n\nBy positively identifying the IDE's own server instead of guessing, Claude Code can safely grant it default permissions (like running code) without prompting, while still treating unrecognized MCP servers cautiously.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}