{"version":"2.1.239","anchor":"remote-control-now-says-when-it-ignored-mcp-servers-you-conf","canonical_anchor":"remote-control-now-says-when-it-ignored-mcp-servers-you-conf","heading":"Remote Control now says when it ignored MCP servers you configured","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-control-now-says-when-it-ignored-mcp-servers-you-conf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote Control now says when it ignored MCP servers you configured\n\nRemote Control now lists MCP servers it ignored instead of silently dropping them.\n\n**What**\n\nWhen a Remote Control session is handed MCP servers it will not use, the status now lists a `(servers not adopted)` entry explaining that only injected Project-scope servers are honoured. Previously those servers were dropped without a word.\n\n**Details**\n\n- The entry only appears when the not-adopted count is above zero.\n- A child process acting as a Remote Control bridge carrier no longer counts non-SDK MCP servers when deciding whether any servers are configured at all.\n\n**Evidence**\n\n`(servers not adopted)`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}