{"version":"2.1.309","anchor":"artifacts-mcp-server-can-replace-the-built-in-artifact-tools","canonical_anchor":"artifacts-mcp-server-can-replace-the-built-in-artifact-tools","heading":"Artifact tools can be provided by an MCP server, with clearer errors when it is missing","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/artifacts-mcp-server-can-replace-the-built-in-artifact-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Artifact tools can be provided by an MCP server, with clearer errors when it is missing\n\nWhen an MCP server takes over the built-in Artifact tools, unknown-tool errors point to it or suggest \/mcp, and artifact links can be read through it\n\n**Unclear.** It is not stated when the Artifact tools are replaced by the MCP server.\n\n**What**\n\nArtifacts are pages Claude can create and share. Claude Code can now have its built-in Artifact tools replaced by an MCP server, an outside program that supplies tools. When that happens:\n\n- If Claude tries to use an Artifact tool that is not there, the error points it to the matching tools on that server instead.\n\n- If that server is not connected, the error says the Artifacts tools are not available right now and suggests `\/mcp`, the command that manages MCP server connections.\n\n- Reading a claude.ai artifact link can be sent to one of that server's tools.\n\n**Why**\n\nIt shows that Artifact support is moving toward a separate server hosted by the desktop app.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}