{"version":"2.1.309","anchor":"webfetch-of-an-artifact-url-points-to-an-mcp-tool-when-one-i","canonical_anchor":"webfetch-of-an-artifact-url-points-to-an-mcp-tool-when-one-i","heading":"Fetching a claude.ai artifact link now points Claude to an artifact reading tool","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/webfetch-of-an-artifact-url-points-to-an-mcp-tool-when-one-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Fetching a claude.ai artifact link now points Claude to an artifact reading tool\n\nWhen WebFetch hits a claude.ai artifact link, the message now names an available artifact-reading tool and checks your permission rules for it\n\n**What**\n\n`WebFetch` is the tool Claude uses to download a web page. It cannot read claude.ai artifacts, which are pages and documents published from Claude. When it is given an artifact link, its message changes depending on what is available:\n\n- If an MCP tool that can read artifacts is available, the message names that tool and the artifact's short identifier from the link. MCP is a way of connecting outside tools to Claude Code.\n\n- If not, the message still gives the old advice to read it with `action: \"read\"` and the link.\n\nYour permission rules for that MCP tool are also checked.\n\nThe stock description of `WebFetch` itself has not changed in this release.\n\n**Why**\n\nIn sessions that have an artifacts tool connected, Claude is pointed straight at a tool that can open the artifact, instead of being given advice that may not apply there.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}