{"version":"2.1.304","anchor":"artifact-rows-published-via-mcp-now-open-through-the-cloud-a","canonical_anchor":"artifact-rows-published-via-mcp-now-open-through-the-cloud-a","heading":"Artifacts published through MCP open the same way as cloud ones","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/artifact-rows-published-via-mcp-now-open-through-the-cloud-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Artifacts published through MCP open the same way as cloud ones\n\nOpening an artifact published through an MCP server now uses the same path as artifacts from cloud sessions\n\n**Unclear.** It is not clear whether anything in this version marks an artifact as published through MCP.\n\n**What**\n\nMCP (Model Context Protocol) is a way to connect Claude Code to outside tools and services. Before, only items in the artifacts list that came from a cloud session were opened through the cloud path; everything else was opened directly from its link. Items published through MCP now take the cloud path too.\n\n**Why**\n\nArtifacts published through MCP now get the same opening behavior as those from cloud sessions.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}