{"version":"2.1.310","anchor":"artifact-route-can-now-resolve-to-artifacts-mcp","canonical_anchor":"artifact-route-can-now-resolve-to-artifacts-mcp","heading":"claude.ai artifacts can now be reached 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-route-can-now-resolve-to-artifacts-mcp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### claude.ai artifacts can now be reached through an MCP server\n\nClaude Code now has a second route for claude.ai artifacts, through an MCP server, beside the built-in Artifact tools\n\n**Unclear.** What decides whether a session uses the MCP route or the built-in Artifact tools is not stated.\n\n**What**\n\nArtifacts are pieces of content created on claude.ai. Claude Code used to reach them only through its built-in Artifact tools. It can now route them through an MCP server instead, MCP (Model Context Protocol) being a way to connect Claude Code to outside tools.\n\n**Why**\n\nIn some setups, artifacts are served through an MCP server rather than the built-in tools.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}