{"version":"2.1.310","anchor":"artifact-tool-errors-and-prompts-now-cover-the-artifacts-mcp","canonical_anchor":"artifact-tool-errors-and-prompts-now-cover-the-artifacts-mcp","heading":"Clearer guidance when claude.ai artifacts are read through an MCP server","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/artifact-tool-errors-and-prompts-now-cover-the-artifacts-mcp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Clearer guidance when claude.ai artifacts are read through an MCP server\n\nClaude now gets guidance for reading claude.ai artifact links through an MCP server, and clearer messages when those tools change\n\n**What**\n\nArtifacts are pieces of content created on claude.ai and shared by link. MCP (Model Context Protocol) is a way to connect Claude Code to outside tools. Claude now has a version of its artifact instructions that tells it to read claude.ai artifact links with the artifacts MCP server's tool. The messages shown when an artifact tool cannot be found also changed:\n\n- They say when the MCP server is no longer available in the session and the built-in Artifact tools are back.\n\n- They point Claude to the web-fetch tool when the MCP server refuses to read a link.\n\n**Why**\n\nClaude gets better directions on which tool to use when the artifact tools are swapped for MCP ones, instead of stalling on a missing tool.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}