memoire
The memoire server provides a comprehensive suite of tools for design system management, Figma integration, code generation, and AI-powered analysis.
Figma Integration: Pull design systems (tokens, components, styles) from a connected Figma file, capture screenshots, inspect selected nodes, browse the file tree, and execute arbitrary JavaScript via the Figma Plugin API.
Spec Management: List, create, retrieve, and validate component, page, and dataviz specs with Zod schema validation.
Code Generation: Generate shadcn/ui + Tailwind component code (React/Vue/Svelte) from saved specs, organized by atomic design level.
Token Management: Get, update, and sync design tokens to a Tailwind config theme extension, with optional push back to Figma.
AI Visual Analysis: Analyze Figma designs with AI vision for general quality, WCAG accessibility compliance, or spec-compliance.
Design System Audit: Run structured audits covering contrast, touch targets, focus indicators, token coverage, and naming conventions.
Design Extraction: Scrape any public URL to extract its design system as a structured
DESIGN.mddocument or raw token JSON.Agent Orchestration: Use a natural language interface to classify, plan, and execute multi-step design workflows.
User Research: Load project-specific insights, personas, and themes to ground design decisions.
Text Layout Measurement: Predict text dimensions, line counts, and overflow risk without a browser or Figma connection.
Health & Usage Monitoring: Check Figma WebSocket bridge health and track AI token usage and estimated session costs.
Extracts design tokens, components, and styles from Figma files via WebSocket bridge, REST API, or plugin, enabling design system synchronization and code generation workflows.
Extracts design systems from Linear's website URLs to generate design documentation and specifications for code generation workflows.
Extracts design tokens, components, and styles from Penpot files using API authentication, providing an alternative design tool integration for design system extraction.
Generates production-ready React components from design specifications with proper props, variants, and component architecture.
Generates production-ready React components using shadcn/ui patterns and includes a shadcn registry server for component management and distribution.
Generates Storybook stories alongside React components for component documentation, testing, and development workflow integration.
Extracts design systems from Stripe's website URLs to generate design documentation and specifications for code generation workflows.
Generates TypeScript-typed React components with proper type definitions and interfaces for type-safe development.
Validates component specifications using Zod schemas to ensure data integrity and consistency throughout the design-to-code pipeline.
memi
Read-only design engineering for coding agents.
Memi is the read-only design engineering audit and skill layer for coding agents. It gives Codex, Claude Code, Cursor, Grok Build, and MCP clients file-anchored interface evidence before they edit UI.
Memi reads the product you already have, identifies accessibility, hierarchy, state, responsive, motion, and token risks, then reruns the same deterministic check after a fix. Your code remains the source of truth.
Supported today: Node 20, 22, and 24 on macOS, Linux, and Windows. Figma and Studio are optional companions.
Links: npm · memoire.cv · current versions · MCP Registry · Agent Skills
Quickstart
Run one audit in any frontend repository:
npx -y @memi-design/cli@2.6.4 diagnose . --json --no-write --fail-on noneYou get a score, normalized finding IDs, confidence, provenance, and file:line evidence. No account, API key, Figma file, global install, or daemon is required.
Keep the workflow available to your coding agent:
npx skills add memi-design/memi --skill audit-frontend-designThen ask:
Audit this frontend before editing it. Prioritize the five fixes that will matter most to users.
Focused skill | Use it when |
| Find interface risks before changing UI |
| Load compact product-system context |
| Gate pull requests with deterministic evidence |
| Build and verify native Apple interfaces |
Compatible with the shadcn registry and v0 design systems.
If Memi catches a real interface issue in your project, star the repository and share the finding. That is the most useful signal for deciding what to improve next.
Related MCP server: SIN-Code-Frontend-Design-Skill
What Memi catches
Signal | Example evidence |
Accessibility | Missing labels, reduced-motion fallbacks, focus and contrast risks |
Interface craft | Weak hierarchy, spacing drift, brittle responsive behavior |
Product states | Missing loading, empty, error, success, and permission states |
Design systems | Token drift, raw values, inconsistent component usage |
Routes and components | App graph, duplicated patterns, risky change surfaces |
Pull requests | New debt only, SARIF annotations, step summary, HTML report |
The first command is deliberately read-only. Write-capable scaffolds and Figma operations are separate, explicit workflows.
How it works
Inspect - build an evidence graph from source, routes, styles, and local design-system files.
Find - report normalized issues with severity, confidence, provenance, and
file:line.Correct - let a human or coding agent make a scoped change.
Verify - rerun the same command and compare the evidence.
No LLM is used in the deterministic CI enforcement path.
Choose your integration
Surface | Start here | Best for |
One-time CLI audit |
| Trying Memi without installing |
Global CLI |
| Daily local use |
Agent Skill |
| Codex, Claude, Cursor, and compatible agents |
GitHub Action |
| Pull-request design CI |
MCP server |
| Any MCP client |
Studio |
| Supervised macOS workflows |
The CLI and focused skills are primary. Studio, Figma, research, scaffolding, registries, and the larger tool router are deeper paths.
Design CI
Pin the release commit so every pull request runs the same code:
name: design
on: [pull_request]
permissions:
contents: read
jobs:
memi:
runs-on: ubuntu-latest
permissions:
contents: read
security-events: write
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
fetch-depth: 0
- uses: memi-design/memi@ec4d804220bfbf08be810ceb692a338cf186e794 # v2.6.4
with:
version: "2.6.4"
report: true
upload-sarif: trueThe Action adds code-scanning annotations, a step summary, and a memi-design-health artifact. Existing debt can be baselined while new debt fails the gate.
GitHub Action guide · CI recipes · team rollout
Agent and MCP setup
Install a complete project kit:
memi agent install codex --project .
memi agent install claude-code --project .
memi agent install cursor --project .
memi agent install grok-build --project .Start the local MCP server without Figma:
memi mcp start --no-figma{
"mcpServers": {
"memoire": {
"command": "memi",
"args": ["mcp", "start", "--no-figma"]
}
}
}Codex plugin marketplace:
codex plugin marketplace add memi-design/memi --ref main --sparse .agents/plugins --sparse plugins/memoireAgent stack guide · copy-paste recipes · full skill router
Proof you can inspect
design-sandbox - runnable Next.js, Tailwind, shadcn, MCP, and Agent Skills integration.
Release gates - package, provenance, clean install, MCP, plugin, binary, and public-surface checks.
Current release truth - one source for npm, GitHub, Action, Studio, and website versions.
Audit reports - timestamped findings, evidence gaps, score caps, and owners.
llms.txt- compact machine-readable product map.
Trust defaults
Read-only audit by default
No npm install-time lifecycle scripts
No account or API key for the first audit
No source upload or covert telemetry
Figma installation and connection are explicit
Agent kit writes support
--dry-run --jsonImmutable Action pins and release provenance
MIT core with third-party boundaries documented in NOTICE
Community
Useful contributions include reproducible audit fixtures, framework adapters, skill improvements, accessible UI cases, shader and motion checks, and real before/after reports.
More commands
Command | What it does |
| App-quality graph and file-anchored findings |
| UX tenets and product-state risks |
| Hierarchy, rhythm, convention, and responsive critique |
| Extract tokens, aliases, modes, and drift |
| Compact evidence contract before UI work |
| Dry-run Atomic Design scaffold |
| Apple-platform design brief |
| Export a shadcn-compatible registry |
| Research-to-design package |
| Baseline-aware pull-request gate |
| Local MCP server |
Install without npm
curl -fsSL https://memoire.cv/install.sh | sh
brew install memi-design/memi/memoire
docker run --rm -it -v "$PWD:/work" -w /work ghcr.io/memi-design/memi --helpLicense
Studio interface references and adapted components include Hermes WebUI and the MIT Warp UI framework boundary around warpui_core and warpui; Warp AGPL application and client code is not copied into Memi.
MIT. See NOTICE for optional adapters and complete third-party attribution.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/memi-design/memi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server