{"version":"2.1.312","anchor":"mcp-skill-metadata-and-artifact-publish-manifest-gain-versio","canonical_anchor":"mcp-skill-metadata-and-artifact-publish-manifest-gain-versio","heading":"Published artifacts record a version, and MCP skills can carry one","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/mcp-skill-metadata-and-artifact-publish-manifest-gain-versio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Published artifacts record a version, and MCP skills can carry one\n\nPublished artifact records now keep a version, MCP tool and type, and Claude Code accepts a name and version for MCP skills\n\n**What**\n\nMCP, the Model Context Protocol, is a way to connect outside tools to Claude Code. Claude Code now accepts details about an MCP skill: a name, a version and, optionally, a description of the server it comes from. When those details are not in the expected shape, the tool is recorded as an MCP skill anyway.\n\nWhen an artifact is published, its record now also stores a version, the MCP tool involved and a type. The version returned is the one supplied, or \"1\" if none is given. Before, it was always \"1\".\n\n**Why**\n\nArtifacts and MCP skills can now carry version numbers instead of all being treated as version 1.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}