Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.304entry #18

Claude Code v2.1.304 ·

Artifact tools from an MCP server can stand in for the built-in ones

When an MCP server supplies artifact tools, Claude Code can hide its built-in artifact tools and apply your permission rules to the MCP ones instead

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

Unclear It is not clear what decides whether the MCP tools replace the built-in artifact tool, or whether that is on by default.

What

Artifact access in Claude Code can now come from tools supplied by an MCP server, which is an outside program that adds tools to Claude Code, instead of from the built-in artifact tool.

  • When an MCP server supplies read_artifact, get_artifact or read_file, the built-in artifact tools can be hidden.
  • When the MCP tools take over, the permission check asks nothing more if your permission rules already cover those tools, and otherwise works as it did for the built-in tool.
  • WebFetch's note about artifact links now names whichever read tool is in use, rather than always the built-in one.
  • Automatic reactions to artifacts are switched off while the built-in artifact tools are hidden this way, as well as when you have turned them off yourself.
Why

This prepares artifact access to move to tools served over MCP. If you write permission rules for artifacts, those rules may need to cover the MCP tool names as well as the built-in one.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what decides whether the MCP tools replace the built-in artifact tool, or whether that is on by default.

See this entry in the whole of v2.1.304 →

Feedback