{"version":"2.1.221","anchor":"routines-connector-list-says-available-not-connected","canonical_anchor":"routines-connector-list-says-available-not-connected","heading":"Routines connector list says \"available\", not \"connected\"","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/routines-connector-list-says-available-not-connected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Routines connector list says \"available\", not \"connected\"\n\nRoutines now list MCP servers as \"available\" since they connect only when needed.\n\n**What**\n\nThe connector list shown to routines no longer implies the MCP servers are already connected.\n\n**Details**\n\n- Both the empty-list case and the list header now use \"available\".\n- Matches the new cached MCP state, where servers are connected lazily.\n\n**Evidence**\n\n`Available connectors (usable by routines):`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}