MCP servers that need Artifacts now say why they are skipped…

MCP servers that need Artifacts now say why they are skipped when Artifacts are off

When Artifacts are turned off, an MCP server that connects to them is listed as ignored, with a message naming the settings that can cause it

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

MCPArea: what it touches

ImprovementsKind: in v2.1.310, 23 Oct 26

ImprovementsSection of the release

What

An MCP server is an add-on that gives Claude Code extra tools. Some MCP servers connect to Artifacts. When Artifacts are turned off, Claude Code does not connect such a server. It now lists the server as ignored and explains why. The message names three things that can turn Artifacts off:

the enableArtifact setting
the CLAUDE_CODE_DISABLE_ARTIFACT environment variable
a deny rule on Artifact

Separately, a setting can hide the built-in Artifact from MCP. When it is on, Claude Code sets up the built-in Artifact in a different way.

Why

A server that seemed to fail to connect for no reason now comes with an explanation. You can check those three places to find the cause.

See this entry in the whole of v2.1.310 →

The build it came inv2.1.310

23 Oct 2026 · 242 entries, this one is #59.

Use it now6
You'll notice128
Nothing to try yet8
Under the hood100

Either side of it

v2.1.309Older

Open the release →

Names in this entry

settingenableArtifact
Turn the Artifact tool off with a false in any file; no file can turn it back on
envCLAUDE_CODE_DISABLE_ARTIFACT
Set to 1 to turn off the Artifact tool, which publishes session output as a private web page on claude.ai. Once you set it, no settings file turns the tool back on. To turn the tool off from a settings file instead, set enableArtifact to false; the deprecated disableArtifact key also turns it off

Is this right?