Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

Artifact connector declarations accept "dynamic": true

Published artifacts can declare "dynamic": true in capabilities.mcp to call unlisted connectors, with viewers approving each on first use

Group of 2 You'll notice No documentation found New Features
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.283,
What probably matters to youSection of the release

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": true lets the page call connectors the declaration does not list.
  • With "dynamic": true, the "servers" list may be empty. Before, an empty list always failed with no_servers.
  • Any dynamic value other than the JSON boolean true, or leaving it out, is refused with the new dynamic_not_boolean error.
  • 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.

Read from
Names in the bundlecapabilities.mcp
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe capabilities field only appears when an internal setting is on, and it is not clear who has that setting.

See this entry in the whole of v2.1.283 →

Feedback