{"version":"2.1.307","anchor":"artifacts-mcp-server-can-be-filtered-out-by-a-new-gate-with","canonical_anchor":"artifacts-off-setting-now-drops-artifacts-mcp-servers-in-rem","heading":"Turning Artifacts off now disconnects the Artifacts MCP server in remote sessions","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/artifacts-mcp-server-can-be-filtered-out-by-a-new-gate-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Turning Artifacts off now disconnects the Artifacts MCP server in remote sessions\n\nIn Claude Code Remote sessions, switching Artifacts off in settings now leaves out MCP servers that connect to the Artifacts server\n\n**Unclear.** It is unclear whether the new server-controlled switch is the Artifacts-off setting itself or a separate switch that must also be on.\n\n**What**\n\nMCP servers are outside services that give Claude extra tools. When Artifacts are turned off in Claude Code settings, MCP server entries whose address points at Claude Code Remote's Artifacts server are now left out and not connected.\n\n- This only applies when `CLAUDE_CODE_REMOTE` is set, meaning the session runs remotely.\n\n- The skipped server shows the message: \"Ignored: Artifacts are turned off in Claude Code settings, so this server, which connects to Artifacts, is not connected\".\n\n- The log records how many servers were left out, under '[MCP] Artifacts are switched off in settings'.\n\n- The filtering sits behind a new remotely controlled switch, `tengu_clever_yeti`. Nothing has been read about whether it is turned on.\n\n**Why**\n\nIn remote sessions the Artifacts setting can now actually remove the route to Artifacts, rather than leaving its MCP server connected, and the message tells you why the server is not 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"}