{"version":"2.1.321","anchor":"artifacts-off-check-drops-mcp-servers-that-reach-artifacts","canonical_anchor":"artifacts-off-check-drops-mcp-servers-that-reach-artifacts","heading":"Turning off Artifacts now also stops MCP servers that connect to them","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/artifacts-off-check-drops-mcp-servers-that-reach-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Turning off Artifacts now also stops MCP servers that connect to them\n\nWhen Artifacts are turned off in settings or by a deny rule, MCP servers that connect to the Artifacts server are not connected\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Artifacts are a Claude Code Remote feature with their own server. When Artifacts are turned off, either in Claude Code settings or by a deny rule on `Artifact`, Claude Code now leaves out any MCP server set up to connect to the Artifacts server. A deny rule is a permission rule that blocks a tool.\n\nThat server is skipped with the note: \"Ignored: Artifacts are turned off here (Claude Code settings, or a deny rule on Artifact), so this server, which connects to Artifacts, is not connected\". Other servers' Artifact tools are also blocked.\n\n**Why**\n\nTurning off Artifacts now also closes the route through MCP servers, so a deny rule on `Artifact` cannot be bypassed that way. If such a server stops connecting, this is why.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}