{"version":"2.1.310","anchor":"artifacts-disabled-message-for-mcp-server-that-connects-to-a","canonical_anchor":"artifacts-disabled-message-for-mcp-server-that-connects-to-a","heading":"MCP servers that need Artifacts now say why they are skipped when Artifacts are off","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/artifacts-disabled-message-for-mcp-server-that-connects-to-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### MCP servers that need Artifacts now say why they are skipped when Artifacts are off\n\nWhen Artifacts are turned off, an MCP server that connects to them is listed as ignored, with a message naming the settings that can cause it\n\n**What**\n\nAn MCP server is an add-on that gives Claude Code extra tools. Some MCP servers connect to Artifacts. When Artifacts are turned off, Claude Code does not connect such a server. It now lists the server as ignored and explains why. The message names three things that can turn Artifacts off:\n\n- the `enableArtifact` setting\n\n- the `CLAUDE_CODE_DISABLE_ARTIFACT` environment variable\n\n- a deny rule on Artifact\n\nSeparately, a setting can hide the built-in Artifact from MCP. When it is on, Claude Code sets up the built-in Artifact in a different way.\n\n**Why**\n\nA server that seemed to fail to connect for no reason now comes with an explanation. You can check those three places to find the cause.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}