Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.198 Home All releases ←olderv2.1.197 v2.1.199newer→
Claude Code v2.1.198

MCP Tip Improved

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-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
  • The updated situation string 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-discovery tip (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.

See this entry in the whole of v2.1.198 →