loading…
Search for a command to run...
loading…
Design system MCP server. 20 tools: extract design tokens from any URL, pull from Figma or Penpot, generate React + shadcn/ui components from specs, run WCAG au
Design system MCP server. 20 tools: extract design tokens from any URL, pull from Figma or Penpot, generate React + shadcn/ui components from specs, run WCAG audits, sync tokens bidirectionally.
Shadcn-native Design CI for Tailwind apps.
Turn an existing app into a registry that works with shadcn, v0, AI editors, npm, and Mémoire.
Memoire starts from the app you already have. Install the npm package, audit the codebase, export a shadcn-native registry, then install the same components with shadcn, v0, or memi.
npm i -g @sarveshsea/memoire
memi diagnose
memi tokens --from ./src --report
memi shadcn export --out public/r
memi publish --name @you/ds
Primary CTA: @sarveshsea/memoire on npm.
Compatibility targets: shadcn registry, registry item schema, components.json, and v0 design systems.
# shadcn-compatible registry item
npx shadcn@latest add https://your-site.com/r/button.json
# v0 / AI-editor context
memi shadcn serve --port 4014
# Mémoire install path with aliases, npm packages, URLs, GitHub, or local paths
memi registry install Button --from @you/ds
memi add Button --from ./public/r
Most developer teams do not start in Figma. Memoire reads the codebase directly: Tailwind classes, shadcn usage, CSS variables, routes, markup, repeated literals, dark-mode coverage, token aliases, component targets, and registry shape.
# Diagnose an existing app from code
memi diagnose
# Diagnose a running local route / public URL
memi diagnose http://localhost:3000
# Extract the token system from the app and write audit reports
memi tokens --from ./src --output generated/tokens --report
# Export shadcn-compatible registry.json and /r/*.json items
memi shadcn export --out public/r
# Save extracted tokens into .memoire/design-system.json for publish/codegen flows
memi tokens --from ./src --save
Reports are written to .memoire/app-quality/diagnosis.{json,md} and token extraction emits CSS, Tailwind, JSON, Style Dictionary, semantic coverage, scale-health notes, alias graph validation, duplicate-value groups, recommendations, and inferred token candidates. Shadcn export emits registry.json plus installable item JSON files under /r.
After diagnosis, the registry loop is simple: publish the improved design system, mirror shadcn-native registry files, install real components anywhere, then keep the registry updated as the source changes.
npm i -g @sarveshsea/memoire
memi tokens --from ./src --report
memi shadcn doctor
memi shadcn export --out public/r
memi publish --name @you/ds
memi add Button --from @you/ds
Point Memoire at src/, app/globals.css, a built CSS file, http://localhost:3000, or a public URL.
# Install through shadcn directly
npx shadcn@latest add https://cdn.example.com/r/button.json
# Use the same registry as AI design-system context
memi shadcn serve --from @you/ds
# Install through Memoire when you want alias/package/URL/GitHub resolution
memi registry install Button --from @you/ds
npm i -g @sarveshsea/memoire
# Publish your Figma file to npm
npx @sarveshsea/memoire publish --name @you/ds --figma https://figma.com/design/xxx --push
# From any project, drop working code in
npx @sarveshsea/memoire add Button --from @you/ds
# → src/components/memoire/Button.tsx (real working code, not a spec)
npm i -g @sarveshsea/memoire
memi theme import ./tweakcn-export.css --name "Acme Theme"
memi theme publish "Acme Theme" --package @you/theme
memi add Button --from @you/theme
A registry bundles tokens (W3C DTCG JSON + Tailwind v4 @theme CSS), component specs, and real generated code for React / Vue / Svelte. Publishable to npm, GitHub, or any static host.
@memoire-examples/starter-saas — neutral SaaS starter. Install with memi add Button --from @memoire-examples/starter-saas. Source: examples/presets/starter-saas@memoire-examples/docs-blog — editorial docs/blog kit. Install with memi add Button --from @memoire-examples/docs-blog. Source: examples/presets/docs-blog@memoire-examples/dashboard — high-contrast analytics dashboard. Install with memi add Button --from @memoire-examples/dashboard. Source: examples/presets/dashboardMore examples and the featured fallback catalog live in examples/.
tweakcn is the visual theme editor for shadcn/ui. Memoire now treats tweakcn as a full workflow, not just a publish flag:
# Import from a tweakcn CSS export or share URL
memi theme import ./tweakcn-export.css --name "Acme Theme"
memi theme import https://tweakcn.com/r/themes/xxx --name "Acme Theme"
# Validate, preview, diff, and generate packaged variants
memi theme validate "Acme Theme"
memi theme preview "Acme Theme"
memi theme variants "Acme Theme"
# Apply it into the current workspace or publish it to npm
memi theme apply "Acme Theme"
memi theme publish "Acme Theme" --package @you/theme
Theme import handles both Tailwind v3 (:root { --primary: ... }) and v4 (@theme { --color-primary: ... }) exports, including :root + .dark multi-mode themes. If you want the one-shot path, memi publish --theme <path-or-url> still works.
Demo scripts for recording and reuse live in docs/DEMOS.md. No-Figma proof examples live in docs/PROOF.md.
Claude Design, Figma Make, Lovable, Bolt, Replit Agent, and v0 are useful for fast first passes. Memoire is for the part after that first pass, when the output has to survive beyond a single prompt or canvas session.
If your team needs better visual quality, versioned tokens, installable components, tweakcn theme packaging, and cross-tool design system context, that is the Memoire wedge.
| Input | Output |
|---|---|
| Existing shadcn/Tailwind app | Design debt diagnosis with scores, issues, reports, and visual direction options |
| Existing CSS/code/URL | Extracted design tokens with modes, aliases, semantic coverage, scale health, and Style Dictionary export |
| Figma file | npm-ready design system registry with tokens, specs, and real components |
| tweakcn theme | A first-class workflow: import, preview, diff, validate, apply, variants, publish |
| Any public URL | DESIGN.md plus an optional starter registry scaffold |
| JSON specs | React + TypeScript + Tailwind components (shadcn/ui) |
| Generated registries | Installable components for React / Vue / Svelte |
npm i -g @sarveshsea/memoire
memi diagnose # audit the current app from code
memi diagnose http://localhost:3000 # audit a running route or public URL
memi design-doc https://linear.app # extract any site's design system
memi tokens --from ./src --save # extract app tokens into the registry
memi tokens --from ./src --report # write token-extraction.report.{md,json}
memi go # figma -> tokens -> specs -> components -> preview
memi go --rest # same thing, no figma desktop needed
memi go --penpot # same thing, from penpot
memi tokens # export as CSS / Tailwind / JSON / Style Dictionary
No Node, no npm, no admin rights.
# macOS / Linux — auto-patches your shell profile, verifies SHA256
curl -fsSL https://memoire.cv/install.sh | sh
# Windows (PowerShell) — auto-adds to user PATH
irm https://memoire.cv/install.ps1 | iex
# Homebrew (macOS / Linux)
brew install sarveshsea/memoire/memoire
# Docker (air-gapped envs where only ghcr.io is reachable)
docker run --rm -it -v "$PWD:/work" -w /work ghcr.io/sarveshsea/memoire --help
# Self-update once installed
memi upgrade
Manual download if curl, brew, and docker are all blocked — grab the archive from GitHub Releases:
| Platform | Archive |
|---|---|
| macOS (Apple Silicon) | memi-darwin-arm64.tar.gz |
| macOS (Intel) | memi-darwin-x64.tar.gz |
| Linux (x86_64) | memi-linux-x64.tar.gz |
| Windows (x64) | memi-win-x64.zip |
Verify with SHA256SUMS.txt (attached to every release). Extract, add memi to PATH, run memi connect. The skills/, notes/, plugin/, preview/ directories must stay next to the binary — Mémoire loads them at runtime.
Memoire also runs as an MCP server, so your AI assistant can work directly with your design system after the registry workflow is in place.
memi mcp config --install # writes .mcp.json, done
Or add manually to .mcp.json:
{
"mcpServers": {
"memoire": {
"command": "memi",
"args": ["mcp", "start"]
}
}
}
Tools include: pull_design_system, generate_code, create_spec, get_tokens, compose, design_doc, run_audit, capture_screenshot, analyze_design, and more in the docs.
| Command | What it does |
|---|---|
memi setup |
Full onboarding: token, file, plugin, bridge, MCP config, test pull |
memi init |
Initialize workspace with starter specs |
memi diagnose [target] |
Diagnose design debt in an existing web app from code or URL |
memi connect |
Start Figma bridge (auto-discovers plugin on ports 9223-9232) |
memi pull |
Extract tokens, components, styles from Figma |
memi pull --rest |
Pull via REST API -- no plugin, no Figma Desktop |
memi pull --penpot |
Pull from Penpot (needs PENPOT_TOKEN + PENPOT_FILE_ID) |
memi spec <type> <name> |
Create a component, page, or dataviz spec |
memi generate [name] |
Generate shadcn/ui code + Storybook stories from specs |
memi generate --no-stories |
Generate without Storybook stories |
memi preview |
Start preview gallery + shadcn registry server |
memi theme <subcommand> |
tweakcn workflow: import, preview, validate, diff, apply, variants, publish |
memi go |
Full pipeline in one command |
memi export |
Export generated code into your project |
memi tokens |
Export registry tokens as CSS / Tailwind / JSON / Style Dictionary (W3C DTCG) |
| `memi tokens --from <file | dir |
memi validate |
Validate all specs against schemas |
| Command | What it does |
|---|---|
memi design-doc <url> |
Extract design system from any URL into DESIGN.md |
memi design-doc <url> --spec |
Also write a DesignSpec JSON for codegen |
memi extract <url> |
Alias for design-doc |
| Command | What it does |
|---|---|
memi sync |
Full sync: Figma + specs + code |
memi sync --live |
Watch and sync continuously |
memi compose "<intent>" |
Agent orchestrator: classify, plan, execute |
memi agent spawn <role> |
Spawn a persistent agent worker |
memi research from-file <path> |
Process Excel/CSV into research |
memi research synthesize |
Synthesize themes and personas |
memi daemon start |
Start daemon with reactive pipeline |
| Command | What it does |
|---|---|
memi status |
Project status overview |
memi doctor |
Health check: project, plugin, bridge |
memi dashboard |
Launch monitoring dashboard |
memi audit |
Design system audit (WCAG, unused specs) |
All commands support --json for structured output.
Every component starts as a JSON spec before code is generated:
{
"name": "MetricCard",
"type": "component",
"level": "molecule",
"shadcnBase": ["Card", "Badge"],
"props": { "title": "string", "value": "string", "trend": "string?" },
"variants": ["default", "compact"]
}
Specs are validated with Zod schemas. Components follow Atomic Design (atom, molecule, organism, template, page).
src/
engine/ Core orchestrator, registry, sync, pipeline
figma/ WebSocket bridge + REST client + Penpot client
agents/ Intent classifier, plan builder, task queue
mcp/ MCP server (tools, resources, stdio)
codegen/ shadcn/ui mapper, Storybook, dataviz, pages
research/ Research engine (Excel, stickies, web)
specs/ Spec types, Zod schemas, 62-component catalog
preview/ Preview gallery, API server, shadcn registry
notes/ Downloadable skill packs
commands/ CLI command surface
plugin/ Figma plugin (Widget V2)
Quickstart -- Examples -- Launch Pack -- Changelog
MIT
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"memoire": {
"command": "npx",
"args": []
}
}
}Extract design specs and assets
An Open-Sourced UI to install and manage MCP servers for Windows, Linux and macOS.
Build, validate, and deploy multi-agent AI solutions on the ADAS platform. Design skills with tools, manage solution lifecycle, and connect from any AI environm
MCP Bundles: Create custom bundles of tools and connect providers with OAuth or API keys. Use one MCP server across thousands of integrations, with programmatic