You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.309,
What probably matters to youSection of the release
Unclear It is not known whether this is switched on for users or still held behind a further setting.
What
MCP (Model Context Protocol) is the way Claude Code connects to outside tools. Claude Code can now add an Artifacts MCP server by itself. It does this when the artifact tool is available and your organization's policy allows it. When the server is in use, its tools replace the built-in artifact tool. Claude Code switches back to the built-in tool if the server is missing, has failed or needs you to sign in.
The server is not added in these cases:
remote sessions
the desktop app
managed or strict MCP configuration
safe mode or bare mode
Some of its tools come with permissions already set:
delete_asset and delete_artifact ask before running
read_shared_artifact is blocked
Each artifact Claude publishes is listed in the session. If a request is refused, the message points you to /login, /permissions and /config.
Why
Reading, writing and deleting artifacts can now go through MCP tools that follow their own allow, ask and deny rules. You can manage those rules in /permissions.
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 known whether this is switched on for users or still held behind a further setting.
