{"version":"2.1.283","anchor":"artifacts-dynamic-connector-declarations-let-viewers-approv","canonical_anchor":"artifacts-dynamic-connector-declarations-let-viewers-approv","heading":"Artifacts can ask each viewer to approve connectors they did not list","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/artifacts-dynamic-connector-declarations-let-viewers-approv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Artifacts can ask each viewer to approve connectors they did not list\n\nAn artifact's connector declaration can now be marked dynamic, so viewers approve unlisted connectors at first use instead of those calls failing\n\n**Unclear.** It is not clear whether the Artifacts feature itself is available to every account.\n\n**What**\n\nAn artifact is a page Claude publishes. Its manifest can list MCP servers, also called connectors, which let the page reach outside tools and data. That list can now be marked `dynamic`.\n\nWith a dynamic declaration:\n\n- Publish checks no longer say that calls to connectors missing from the manifest fail for every viewer. They say each viewer is asked to approve the connector the first time it is used.\n\n- A name the viewer has no connector for is refused.\n\n- The publish result tells Claude to tell you which connectors the page calls and that those integrations are unverified.\n\n- The capability summary shows \"any connector the viewer approves\".\n\n**Why**\n\nPages can now use connectors that were not declared ahead of time, with each viewer approving them. Because these integrations are unverified, Claude is told to point them out to you.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}