Claude Code 2.1.295 MCP changes: a checklist for Sume

Three MCP changes in Claude Code 2.1.295 (Oct 8) and what each means for a connection to Sume's hosted server. A short table to run through after upgrading.

4 min readSume
All posts

Claude Code 2.1.295 changed three things about MCP, per its changelog. Only two can touch Sume's hosted server in a way you can feel: longer tool descriptions through tool search, and a 30-second backoff after drops in headless mode. The third concerns WebSocket servers, which Sume is not.

What changed, and does it touch Sume?

Read each row against the hosted MCP at https://mcp.sume.com/mcp.

Claude Code 2.1.295, Oct 8 2026 (read 2026-10-09)
ChangeEffect on Sume
Tool-search descriptions cut at 16,384 characters (was 2,048)Read the descriptions from tools_list after upgrading; more of each one can now reach the model
WebSocket MCP messages over 16 MiB close the connectionNone; Sume's server is HTTP at /mcp and returns URLs for media
Remote MCP in headless/SDK backs off up to 30 s after dropsReuse the same idempotency_key on retries

What is worth testing?

Run these two after upgrading:

  • Call mcp_health and tools_list; compare the tool count to the last run.
  • Drop the network mid-run in CI and confirm the retry reuses its key and reads the job instead of creating a second one.

Which version is the floor?

2.1.288 (Oct 2) fixed MCP calls that sometimes ran twice when a remote result was over 16 MB or unparsable, and 2.1.292 (Oct 6) leaves out MCP tool names over 128 characters with an MCP error. Check the longest tool name in your tools_list output against that 128-character limit.

Where are the gates?

Unchanged: idempotency_key on paid and write tools, dry_run previews, max_spend_usd when you send it. See MCP tools and gates.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume