The 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.
Details
- The
mcp-expandtip fires whene.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 - The updated
situationstring now contains the explicit constraint:"The configured servers are an eligibility signal only — 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" - 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
- Feature text presented to the user:
"You can add more MCP servers for services your current ones do not cover."with action/mcp - Contrast with the
mcp-discoverytip (no MCP at all,e.mcpClients.length === 0) which introduces MCP from scratch
Evidence
Updated tip situation string (search for "The configured servers are an eligibility signal only"); when condition e.mcpClients.length >= 1 in the SXn tip array
Strings lifted out of the shipped bundle, so the claim above can be checked against them.