{"version":"2.1.299","anchor":"artifact-mcp-wire-relay-for-frame-requests","canonical_anchor":"artifact-mcp-wire-relay-for-frame-requests","heading":"Artifact requests can travel as MCP tool calls","tier":"soon","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/artifact-mcp-wire-relay-for-frame-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Artifact requests can travel as MCP tool calls\n\nSome artifact requests, such as pinning and listing, can be sent as MCP tool calls through a new relay, with separate tracking for each kind\n\n**What**\n\nArtifacts are items Claude Code can create, pin and publish. Requests about them have gone to `\/api\/frame`. A new relay can carry some of these requests as MCP `tools\/call` requests instead. MCP (Model Context Protocol) is the standard Claude Code uses to talk to outside tool servers.\n\n- Pinning or unpinning an artifact goes as `pin_artifact` or `unpin_artifact`.\n\n- Deploying (deploy\/direct) goes as `publish_version`.\n\n- Listing frames and listing types go as `list_artifacts` and `list_types`.\n\n- The relay is skipped inside remote sessions, and its fallback is off.\n\n- Tracking for the relay is now split by kind of request (listing, pin, publish and tool listing) instead of being one combined record.\n\nThe relay sits behind the switch `tengu_cobalt_plinth_teasel`. Nothing has been read about that switch, so it is not known whether the relay is in use.\n\n**Why**\n\nThe relay changes how artifact requests travel. If it is turned on, pinning, publishing and listing artifacts would run over MCP instead of direct requests.\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}