Log inSubmit server
Memi logo

Memi

by sarveshsea

Audits frontend repositories, extracts design context, and gives coding agents evidence-based UI and accessibility findings.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Memi

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sarveshsea-memi": {
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @memi-design/cli@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 24d ago.

Overview

The sarveshsea/memi MCP server gives coding agents repository-aware design-system context for frontend work. It supports UI audits, Tailwind token extraction, shadcn registry workflows, Figma and Paper context, design documentation, and interface-quality diagnostics through 46 MCP tools. Local diagnosis uses deterministic rules and returns normalized findings with confidence, provenance, and file-and-line evidence without requiring an API key or model call. Reach for it when an agent needs to understand an existing interface, avoid duplicate components, or verify design and accessibility changes before merge.

Use cases

  • Audit a frontend repository before an agent edits it
  • Extract existing Tailwind and DTCG design tokens
  • Check whether a component should be reused before generation
  • Run interface-quality checks in pull requests

Key features

  • Frontend UI and accessibility diagnosis
  • Tailwind and CSS/DTCG token extraction
  • shadcn registry and component-reuse checks
  • Figma and Paper context envelopes
  • Repository-aware agent briefs
  • JSON, receipt, artifact, and SARIF reporting

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

16/17 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @memi-design/cli@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars49Stargazers on the source repository.
npm downloads634Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Memi works

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:

Terminal
npx -y @memi-design/cli@latest diagnose . --json --no-write --fail-on none
Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Memi

sarveshsea/memi is an MCP server that connects coding agents to frontend repository design context and interface diagnostics. Its main capabilities cover UI audits, Tailwind token extraction, shadcn registry workflows, Figma or Paper context, design briefs, and quality findings with file-and-line evidence. Local diagnosis uses deterministic rules without a model call or API key.

Install its CLI through npm with `npx -y @memi-design/cli@latest`, then run the documented `diagnose` command in a frontend repository. The README also provides `npx skills add memi-design/memi --skill audit-frontend-design` for the related agent skill. A global installation or daemon is not required for the first audit.

Local diagnosis does not require a model call, API key, or model fee, but the initial npm installation requires registry access.

It documents a locked stdio MCP workflow and explicitly discusses Codex, so compatibility with Cursor should be verified against the client’s MCP setup rather than assumed from the repository excerpt.

Related MCP servers

All in Architecture & Design All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMemi AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sarveshsea-memi?style=directory)](https://allmcps.com/mcp/sarveshsea-memi)
HTML Embed
<a href="https://allmcps.com/mcp/sarveshsea-memi"><img src="https://allmcps.com/api/badge/sarveshsea-memi?style=directory" alt="Memi on AllMCPs" /></a>