{"version":"2.1.198","anchor":"mcp-tip-improved","canonical_anchor":"mcp-tip-improved","heading":"MCP Tip Improved","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.198\/e\/mcp-tip-improved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.198","markdown":"### MCP Tip Improved\n\nThe MCP expansion tip (shown when a user is manually pasting data from a service already coverable by an MCP server) now requires the tip to name the specific service being bridged, rather than citing the user's existing unrelated servers.\n\n**Details**\n\n- The `mcp-expand` tip fires when `e.mcpClients.length >= 1` (at least one MCP server is already configured) and the user is manually pasting data the model determines could be sourced via MCP\n- The updated `situation` string now contains the explicit constraint: `\"The configured servers are an eligibility signal only \u2014 the tip must name the service the user is manually bridging (e.g. 'the GitHub MCP would let you query issues directly'), never cite their existing unrelated servers as justification\"`\n- This prevents the model from producing a generic tip like \"you already have MCP, add more\" and forces it to identify and name the specific unmapped service\n- Feature text presented to the user: `\"You can add more MCP servers for services your current ones do not cover.\"` with action `\/mcp`\n- Contrast with the `mcp-discovery` tip (no MCP at all, `e.mcpClients.length === 0`) which introduces MCP from scratch\n\n**Evidence**\n\nUpdated tip situation string (search for `\"The configured servers are an eligibility signal only\"`); `when` condition `e.mcpClients.length >= 1` in the `SXn` tip array"}