# sarveshsea/memi [Health: Active]

**Category:** 📐 Architecture & Design  
**Repository:** https://github.com/sarveshsea/memi  
**GitHub Stars:** 49  
**npm Downloads (last month):** 634  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sarveshsea-memi

## Description
Design-system memory for coding agents with 46 MCP tools for UI audits, Tailwind token extraction, shadcn registry workflows, Figma context, design docs, and interface-quality diagnostics.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "memi": {
    "command": "npx",
    "args": ["-y","@memi-design/cli@latest"]
  }
}
```

## Documentation

## What sarveshsea/memi MCP server does

The sarveshsea/memi MCP server supplies design context and frontend inspection capabilities for coding agents. Its documented scope covers UI audits, Tailwind token extraction, shadcn registry workflows, Figma context, design documentation, and interface-quality diagnostics. The repository describes 46 MCP tools, while the 2.8 frontend workflow exposes a smaller locked set of read tools by default.

A local diagnosis scans the frontend repository and reports findings with normalized IDs, confidence values, provenance, and `file:line` evidence. This lets an agent work from specific observations instead of inferring the interface from an undifferentiated repository dump. The checks are non-destructive by default and are intended to be rerun after edits.

## How it works

The sarveshsea/memi MCP server uses deterministic local rules for source diagnosis. The diagnosis does not make a model call and does not require an API key or model fee.

The frontend workflow can combine repository exports, component props, CSS or DTCG tokens, and CSF stories into a JSON brief. Explicit mappings are checked against current exports, required props, token references, and optional source hashes. Registry specifications marked as mapped can signal that an existing component should be reused rather than generated again.

Figma or Paper context can be supplied through a validated envelope. The documented workflow does not require an additional model session or a bundled connector for that context. Quality scores cover assessed categories only; browser verification remains unassessed until it is actually run.

## Setup and configuration

The initial audit can run directly in a frontend repository with the Memi CLI:

```bash
npx -y @memi-design/cli@latest diagnose . --json --no-write --fail-on none
```

```bash
npx skills add memi-design/memi --skill audit-frontend-design
```

For the published 2.8 frontend beta, the documented package version is `2.8.0-beta.2`; stable remains `2.7.9`. The beta is explicitly not a stable release. A version check and frontend brief can be run with the pinned beta package. The locked stdio workflow starts without sockets or project writes, and four read tools are available without grants.

No account, API key, Figma file, global installation, or daemon is required for the first local audit. Installing from npm still requires registry access.

## Tools and capabilities

The sarveshsea/memi MCP server is documented as providing tools for:

- Auditing frontend interfaces and reporting file-anchored design or accessibility risks.
- Extracting Tailwind design tokens and working with CSS or DTCG token data.
- Inspecting shadcn registry specifications and identifying component-reuse conflicts.
- Supplying validated Figma or Paper context to an agent.
- Creating repository-aware frontend briefs and design documentation.
- Producing metadata-only receipts or JSON reports for repeatable checks.

A GitHub Actions example can run the check on pull requests. The workflow is designed to fail only on newly introduced interface debt and can produce a human-readable artifact. SARIF annotations require the repository to grant `security-events: write`.

## Limitations and notes

The sarveshsea/memi MCP server provides evidence for an agent; it does not replace the repository’s own checks or make design quality universal. Existing custom CSS and component systems do not need to migrate to shadcn.

The 2.8 beta defers many legacy command paths and is not described as a drop-in upgrade for every 2.7 workflow. Managed independent security scanning, SwiftUI parity, full DesignWorkbench certification, and some rendered verification receipts remain pending or unassessed. The published beta also keeps many inventoried CLI paths deferred, so broad grants do not automatically enable them.

_Full upstream README: https://allmcps.com/mcp/sarveshsea-memi/readme_