{"version":"2.1.247","anchor":"ide-auto-connect-hands-its-config-upward-instead-of-writing-","canonical_anchor":"ide-auto-connect-hands-its-config-upward-instead-of-writing-","heading":"IDE auto-connect hands its config upward instead of writing it","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/ide-auto-connect-hands-its-config-upward-instead-of-writing-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### IDE auto-connect hands its config upward instead of writing it\n\nIDE auto-connect hands its config to the caller rather than writing the MCP entry itself.\n\n**What**\n\nAuto-connecting to an IDE no longer writes the MCP entry itself; it passes the connection descriptor to a callback and returns the install state, moving ownership of that entry to the caller. The entry is still recorded as `scope: \"dynamic\"`.\n\n**Evidence**\n\n`scope: \"dynamic\"`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}