design-dna-mcp

design-dna-mcp

Extracts reusable UI patterns from websites into a searchable library using Playwright and Claude, enabling natural-language queries like 'find monospace technical labels'.

Category
Visit Server

README

<div align="center">

<img src="dna.gif" width="200" />

Extract the design DNA of any website — a searchable library of reusable UI patterns, built for Claude.

CI License: MIT Node MCP Verified with MCPJam

<br>

<img src="docs/assets/capture-readout.png" alt="A crawl of linear.app: full-page capture alongside the extracted palette, typefaces, spacing scale, and component candidates" width="100%">

<sub>One crawl_website call on <code>linear.app</code> — full-page capture, 8-color palette, typefaces, spacing scale, 167 motion rules, and the component candidates that come out of it.</sub>

</div>


Design galleries (Godly, Awwwards, Minimal Gallery…) are great sources of ideas but poor databases. You bookmark a site because you liked one thing about it — a navigation treatment, a spacing system, a hover animation — and then you can never find it again.

This MCP server fixes that. Point it at any website and it:

  1. Captures the design evidence with Playwright — screenshots, DOM, computed styles, font hierarchy, color palette, spacing scale, and declared CSS motion
  2. Decomposes it with Claude into reusable design components ("Numbered section index (x.x labels)", "Image reveal hover", "Pill-shaped primary CTA") with category, description, style tags, and metadata
  3. Stores the components you choose to keep in a local SQLite library with vector embeddings
  4. Answers natural-language queries from any MCP client: "find sticky editorial navigation", "monospace technical labels", "sites like a technical product page"

The unit of knowledge is the component, not the website. A website is only evidence.

Example

> crawl_website("https://linear.app")
  capture 1 · 9 screenshots · palette #f7f8f8/#0f1011/… · Inter Variable + Berkeley Mono · 167 motion rules

> extract_components(captureId: 1)
  [navigation]        Dark minimal top navigation            — minimal, dark, swiss, saas
  [typography]        Monospace inline code tag              — monospace, technical, terminal
  [diagram]           Numbered technical figure diagrams     — technical, blueprint, isometric
  [number-treatment]  Numbered section index (x.x labels)    — technical, monospace, editorial
  [motion]            Animated grid-dot background pattern   — technical, ambient, blueprint
  … 18 candidates

> save_component(captureId: 1, saveAll: true)

> find_components("monospace technical labels")
  0.62  [typography]        Monospace inline code tag           https://linear.app/
  0.61  [number-treatment]  Numbered section index (x.x labels) https://linear.app/

Tools

Tool What it does
crawl_website(url) Playwright capture: full-page + section screenshots, DOM, styles, fonts, palette, spacing scale, CSS motion. Versioned per crawl. No API cost.
extract_components(url | captureId, focus?) One Claude vision call decomposes a capture into component candidates. Candidates are cached, not auto-saved — you curate.
save_component(candidateId | captureId+saveAll | component) Persists components to the library with a Voyage embedding. Upserts on (sourceUrl, name).
find_components(query, filters?) Semantic search with optional category/tag/theme/sourceUrl filters.
search_designs(query) Same index grouped by source website — the "sites like this" view.
ping Health check + library size.

Setup

Requires Node 20+ and API keys for Anthropic (analysis) and Voyage AI (embeddings).

git clone https://github.com/olartgabo/design-dna-mcp.git
cd design-dna-mcp
npm install
npx playwright install chromium   # one-time browser download
npm run build

If npm blocks install scripts, approve the native builds once:

npm install-scripts approve better-sqlite3
npm install-scripts approve esbuild
npm rebuild better-sqlite3 esbuild

Register in Claude Code

The most reliable way on any platform (use -s user to enable it in all your projects):

claude mcp add-json design-dna -s user '{"command":"node","args":["/absolute/path/to/design-dna-mcp/dist/index.js"],"env":{"ANTHROPIC_API_KEY":"sk-ant-...","VOYAGE_API_KEY":"pa-..."}}'

Register in Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "design-dna": {
      "command": "node",
      "args": ["/absolute/path/to/design-dna-mcp/dist/index.js"],
      "env": {
        "ANTHROPIC_API_KEY": "sk-ant-...",
        "VOYAGE_API_KEY": "pa-..."
      }
    }
  }
}

Environment variables

Variable Required Default Purpose
ANTHROPIC_API_KEY for extract_components — Claude vision analysis
VOYAGE_API_KEY for save/search — Embeddings
DESIGN_DNA_DATA_DIR no ~/.design-dna-mcp SQLite DB + screenshots
DESIGN_DNA_MODEL no claude-sonnet-5 Analysis model
DESIGN_DNA_EMBEDDING_MODEL no voyage-3.5 Embedding model

The server starts fine without keys — tools that need a missing key fail per-call with a clear error naming the variable. The library is shared across all your projects (it lives in the data dir, not the repo).

<sub>This project was previously named design-research-mcp. The old DESIGN_RESEARCH_* variables still work, and an existing ~/.design-research-mcp library is adopted in place — no migration needed.</sub>

How it works

website ─→ Playwright ─→ capture (screenshots · DOM · styles.json · css/)
                              │
                              ▼
                    distiller (size-capped JSON + ≤6 images)
                              │
                              ▼
                 Claude (one vision call, forced tool-use schema)
                              │
                              ▼
                    candidates (cached, human-curated)
                              │  save_component
                              ▼
              SQLite + sqlite-vec (cosine) + Voyage embeddings
                              │
                              ▼
                find_components / search_designs (MCP)

Design decisions worth knowing:

  • Bounded AI cost — extraction is one Claude call per site (distilled data + a handful of images), never per-element calls.
  • Curation over hoarding — extraction produces candidates; only what you save becomes searchable. saveAll exists when you want everything.
  • Everything local — SQLite + sqlite-vec in a single file, screenshots on disk. No Postgres, no S3, no services.
  • Large payloads stay on disk — tool results carry paths and compact summaries, never base64 blobs.

Cost & rate limits

  • crawl_website is free (local Playwright).
  • extract_components ≈ one claude-sonnet-5 call with ~5–10K input tokens + up to 6 images per site.
  • Embeddings are tiny Voyage calls per save/search — effectively negligible.
  • Voyage's free tier allows ~3 requests/minute; the client retries with long backoff (up to ~70s), so rapid-fire searches feel slow until you add billing to the Voyage account.

Verified with MCPJam

Every tool in this server was exercised over a real stdio transport with MCPJam — schema validation, handshake, and live tool calls — not just unit tests. Reproduce it yourself:

npx @mcpjam/cli tools list --transport stdio --command node --args dist/index.js
npx @mcpjam/cli server doctor --transport stdio --command node --args dist/index.js
npx @mcpjam/cli tools call --transport stdio --command node --args dist/index.js \
  --tool-name crawl_website --tool-args '{"url": "https://example.com"}'

Development

npm test          # 51 offline tests (vitest) — local fixture site, no API keys needed
npm run dev       # run from source via tsx
node scripts/try-crawl.mjs https://linear.app   # crawl real sites (no keys needed)
node scripts/e2e.mjs https://linear.app         # full live loop (needs both keys)
node scripts/mcp-smoke.mjs                      # stdio round-trip smoke test

Built spec-first. The full trail — requirements → design → tasks, with the verification sweep — lives in .claude/specs/design-dna-mcp/, and the original product vision is in docs/VISION.md.

Roadmap (v2)

  • classify_design(url) — style confidence scores (editorial 92%, swiss 85%, …)
  • compare_designs(url1, url2) — shared vs unique patterns
  • recommend_components(project_description) — "I'm building a dark editorial portfolio" → curated component sets
  • Interaction recording — hover/scroll capture with measured easing, duration, stagger
  • FTS5 hybrid search, gallery-site ingestion helpers

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured