What
A published artifact declares which connectors (MCP servers, the outside services Claude can reach) its page may call, under capabilities.mcp. That declaration has a new option:
"dynamic": truelets the page call connectors the declaration does not list.- With
"dynamic": true, the"servers"list may be empty. Before, an empty list always failed withno_servers. - Any
dynamicvalue other than the JSON boolean true, or leaving it out, is refused with the newdynamic_not_booleanerror. - When a page calls servers the declaration does not list, the publish warning now says each viewer will be asked to approve them at first use, instead of saying the calls fail.
- The empty-servers error now ends "is refused" instead of "is always refused".
Why
Artifact authors no longer have to name every connector up front. Instead of a fixed list set at publish time, each viewer decides the first time the page uses a connector.
Names in the bundlecapabilities.mcp
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The capabilities field only appears when an internal setting is on, and it is not clear who has that setting.