Layer
Agent reference
Published registry No server required

The design system, queryable.

DV Layer's MCP service gives coding agents source-backed component examples, tokens, icons, migrations, and architecture guidance. Clients discover its tools at runtime. The reference is published as static files on this origin, so connecting needs no service to be running.

Connect once at user scope.

The client runs beside your agent and reads this origin's published registry, verifying every file against the digests the registry pins. Register it once for your user; repository-local MCP files are intentionally unsupported.

  1. Install the reference client

    One package, taken from this origin's newest verified release. It carries no documentation of its own — everything it answers comes from the registry. 

    Verify the local release before installing.

  2. Register Claude Code

    The explicit user scope makes the same reference available from every repository. 

    claude mcp add --scope user dv-layer -- \
  dv-layer-mcp-stdio --registry /r/v1/

  3. Register any other client

    Codex and other MCP clients take the same stdio command; consult your client's own registration syntax for how it spells this. 

    command: dv-layer-mcp-stdio
args:    ["--registry", "/r/v1/"]

After changing a client registration: start a new Codex or Claude session so its MCP tool inventory is refreshed. Pass --version to pin a client to the release it actually has installed, rather than the newest one published.

A small, explicit service contract.

Running the HTTP service instead is optional — one always-on endpoint for machines you cannot install anything on. It serves the same tools from the same registry, on its own origin. The root explains the service; the transport stays at its standard route.

/
Human-readable service identity with links to documentation and probes.
/mcp
Streamable HTTP MCP transport used by Codex, Claude, and other compatible clients.
/healthz
Liveness probe. Detailed identity is only returned to authorized deployments.
/readyz
Readiness probe confirming that the reference data has loaded successfully.

Working on DV Layer itself?

pnpm local:deploy builds the packages and site, brings up the gateway and MCP service, and verifies both HTTP and MCP protocol behaviour against the published registry. A hosted endpoint at mcp.dv-layer.com keeps the same split origins, and stays behind HTTPS, OAuth 2.1, rate limits, logging, and a tested rollback before any internet exposure.