{"version":"2.1.248","anchor":"mcp-errors-sent-to-remote-control-clients-are-filtered-to-a-","canonical_anchor":"mcp-errors-sent-to-remote-control-clients-are-filtered-to-a-","heading":"MCP errors sent to Remote Control clients are filtered to a fixed list","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-errors-sent-to-remote-control-clients-are-filtered-to-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP errors sent to Remote Control clients are filtered to a fixed list\n\nIn bridge mode, unknown MCP errors are collapsed to \"connection failed\" for remote clients.\n\n**What**\n\nIn bridge mode (`CLAUDE_CODE_ENVIRONMENT_KIND=bridge`), the per-server error map returned for an MCP server update now only passes through known reasons such as \"Blocked by enterprise policy (allowedMcpServers\/deniedMcpServers)\", \"Ignored in hermetic mode (not declared in user config)\" and \"Ignored in a Remote Control session: MCP servers are loaded only from the verified startup config on this machine\". Anything else becomes \"connection failed\". Outside bridge mode the original text is still returned.\n\n**Details**\n\n- Two error shapes are additionally allowed by pattern: `Server status: <status>` and `Server not found: <name>` (name limited to 64 characters of letters, digits, space, underscore, dot and hyphen).\n- Server-name keys are sanitized too and duplicates get a `#2` suffix.\n\n**Evidence**\n\n`Ignored in a Remote Control session: MCP servers are loaded only from the verified startup config on this machine`\n\n- Area: Remote Control\n- Names: `CLAUDE_CODE_ENVIRONMENT_KIND`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}