Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.295 ·

Artifact frame requests can now travel over an MCP connection

Requests for artifact frames can now be sent through an MCP connection when one is available, and fall back to plain HTTP otherwise

Under the hood Internal Changes
JSON All of v2.1.295
Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.295,
Internal ChangesSection of the release
What

When Claude Code asks for an artifact frame, it can now send that request through an MCP connection instead of always using an ordinary web (HTTP) request. MCP, the Model Context Protocol, is the standard way Claude Code connects to outside tools and services.

The request now follows these rules:

  • With the HTTP-only option set, it always goes over plain HTTP.
  • Without that option, if an MCP connection is available for the request, Claude Code sends it there first.
  • If the MCP route returns nothing, Claude Code falls back to plain HTTP.
Why

Artifact requests can now be carried inside an existing MCP connection. When that route gives no answer, the request still goes out over plain HTTP as it did before.

See this entry in the whole of v2.1.295 →

Feedback