{"version":"2.1.314","anchor":"artifacts-mcp-publish-analytics","canonical_anchor":"artifacts-mcp-publish-analytics","heading":"Claude Code records how Artifacts publishing calls turn out","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/artifacts-mcp-publish-analytics","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Claude Code records how Artifacts publishing calls turn out\n\nClaude Code now records whether its Artifacts publishing tools succeed and why the local Artifacts server was not added\n\n**What**\n\nClaude Code now records usage data about its Artifacts tools. It notes whether publishing an artifact, or creating one from a type, worked or failed. It also notes why the local Artifacts MCP server, a tool server running on your own machine, was not added when it is skipped.\n\n**Why**\n\nThis is usage data only and does not change what the tools do.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}