[FEATURE]: way for Claude Code to query an externally-maintained design system (e.g. Claude Design)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem

Claude Design (Anthropic Labs, launched 2026-04-17) reads a team's codebase and design files to extract the design system, then lets
designers/PMs iterate on it inside the studio. The result is an authoritative, evolving design system that lives outside the repo.

Claude Code today has no way to query that system. The only sources of truth CC can read are:

• whatever happens to be in the repo (stale the moment the designer iterates)
• whatever the designer manually exported and committed (lossy, manual, and lags reality)

This creates a one-way asymmetry: repo → Claude Design works, but Claude Design → CC does not. The "design system" ends up forked across
two tools with no sync primitive, and reconciliation falls back to humans copying tokens, components, and layout decisions across by hand.

Why this matters for CC users

A common UI workflow looks like:

1. Designer revises the design system to v2.x in Claude Design
2. PM/designer asks for the new UI to be implemented
3. Developer opens Claude Code to do the work
4. CC has no way to ask "what is v2.x?" — so it either re-derives a stale system from the repo, or the developer pastes screenshots / token

JSON by hand

Step 4 is the part CC could close.

Proposed Solution

The natural shape is an MCP server (presumably owned by the Claude Design team) that CC can consume, exposing roughly:

• get_design_system(version) — tokens, type scale, spacing, components
• list_artifacts(project) — mockups/prototypes with versions
• get_artifact(id) — layout / component tree
• ideally a change feed so CC can notice "designer shipped v2.3, repo is on v2.1"

From CC's side, the ask is:

1. First-class support for a Claude-Design MCP connector once it exists (auth flow, caching, surfacing artifacts to the model in a useful

shape — not just as opaque blobs)

1. A documented convention for "design system context" so CC can prefer the live system over stale repo files when both are present
2. Until the MCP exists: a documented escape hatch (e.g. designer exports tokens to a known path; CC treats it as authoritative) so teams

aren't blocked

Alternative Solutions

Designer exports tokens / artifacts to a committed file or a Drive folder; CC reads from there. Works, but every export is a manual sync
step and the system drifts the moment the designer iterates again.

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

Designer extracts our design system into Claude Design, then iterates it inside the studio — say from v1 to v2.3 (new spacing scale, two
revised components, a tightened color palette). They now need that revision to land in code, either as new UI being built or as an update
sweep across existing components for consistency.

Today, Claude Code has no way to ask "what is v2.3?" The designer has to manually export tokens, screenshots, or component specs and
commit them, and CC reads whatever happens to be on disk — always lagging the designer's actual current state. Claude Code absolutely
needs to be able to query the live design system, not just whatever stale snapshot got exported last.

Additional Context

Related issues

• #52292 (Claude Design share URLs return "not found" to unauthenticated clients) — narrower symptom of the same gap; reports that

individual file share URLs aren't fetchable from CC and floats "Ship a Design MCP server" as one of several fixes. This issue is the
architectural superset: not just file-blob fetch, but a queryable design system as a first-class surface.

• #51980 (Send to Claude Code Web lacks repo picker) — context only. Confirms a one-shot bundle handoff from Claude Design to CC Web exists

today, but it's a one-time export, not an ongoing query channel.

References

• Claude Design launch: https://www.anthropic.com/news/claude-design-anthropic-labs
• Canva MCP partially bridges this (Claude Design → Canva → CC via Canva MCP), but Canva is a destination for finished assets, not a source

of truth for the design system itself.