{"version":"2.1.309","anchor":"artifacts-mcp-server-auto-registered-on-the-laptop-cli","canonical_anchor":"artifacts-mcp-server-auto-registered-on-the-laptop-cli","heading":"Artifacts can run through a built-in MCP server in the terminal","tier":"notice","area":"Artifacts","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/artifacts-mcp-server-auto-registered-on-the-laptop-cli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Artifacts can run through a built-in MCP server in the terminal\n\nClaude Code can set up an Artifacts MCP server itself and use its tools in place of the built-in artifact tool, with preset permissions\n\n**Unclear.** It is not known whether this is switched on for users or still held behind a further setting.\n\n**What**\n\nMCP (Model Context Protocol) is the way Claude Code connects to outside tools. Claude Code can now add an Artifacts MCP server by itself. It does this when the artifact tool is available and your organization's policy allows it. When the server is in use, its tools replace the built-in artifact tool. Claude Code switches back to the built-in tool if the server is missing, has failed or needs you to sign in.\n\nThe server is not added in these cases:\n\n- remote sessions\n\n- the desktop app\n\n- managed or strict MCP configuration\n\n- safe mode or bare mode\n\nSome of its tools come with permissions already set:\n\n- `delete_asset` and `delete_artifact` ask before running\n\n- `read_shared_artifact` is blocked\n\nEach artifact Claude publishes is listed in the session. If a request is refused, the message points you to `\/login`, `\/permissions` and `\/config`.\n\n**Why**\n\nReading, writing and deleting artifacts can now go through MCP tools that follow their own allow, ask and deny rules. You can manage those rules in `\/permissions`.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}