{"version":"2.1.295","anchor":"artifact-frame-requests-can-be-sent-over-an-mcp-row","canonical_anchor":"artifact-frame-requests-can-be-sent-over-an-mcp-row","heading":"Artifact frame requests can now travel over an MCP connection","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/artifact-frame-requests-can-be-sent-over-an-mcp-row","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Artifact frame requests can now travel over an MCP connection\n\nRequests for artifact frames can now be sent through an MCP connection when one is available, and fall back to plain HTTP otherwise\n\n**What**\n\nWhen Claude Code asks for an artifact frame, it can now send that request through an MCP connection instead of always using an ordinary web (HTTP) request. MCP, the Model Context Protocol, is the standard way Claude Code connects to outside tools and services.\n\nThe request now follows these rules:\n\n- With the HTTP-only option set, it always goes over plain HTTP.\n\n- Without that option, if an MCP connection is available for the request, Claude Code sends it there first.\n\n- If the MCP route returns nothing, Claude Code falls back to plain HTTP.\n\n**Why**\n\nArtifact requests can now be carried inside an existing MCP connection. When that route gives no answer, the request still goes out over plain HTTP as it did before.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}