{"version":"2.1.227","anchor":"toggling-one-mcp-server-refreshes-only-its-skills","canonical_anchor":"toggling-one-mcp-server-refreshes-only-its-skills","heading":"Toggling one MCP server refreshes only its skills","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/toggling-one-mcp-server-refreshes-only-its-skills","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Toggling one MCP server refreshes only its skills\n\nToggling one MCP server no longer wipes every other server's cached skills.\n\n**What**\n\nEnabling or disabling an MCP server now invalidates the skills cached for that server specifically, instead of clearing a shared cache. Other servers' skills stay warm.\n\n**Details**\n\n- Skill fetching remains behind the same MCP-skills check that previously guarded it, so nothing new is fetched where MCP skills are off.\n\n**Evidence**\n\n`invalidateMcpSkillsForServer`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}