memi

Name: memi
Author: memi-design

by memi-designversion 2.7.9i★ –iRuns on your computer

Registry nameio.github.memi-design/memi

Install

Overview

Description from the maker (original English)

Memi is the design layer for agentic AI.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Design, images & audio

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "memi": {
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli",
        "mcp",
        "start",
        "--no-figma"
      ]
    }
  }
}

Run this in your terminal

claude mcp add memi -- npx -y @memi-design/cli mcp start --no-figma

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "memi": {
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli",
        "mcp",
        "start",
        "--no-figma"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "memi": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli",
        "mcp",
        "start",
        "--no-figma"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account memi-design, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Design, images & audioi

More stars than 0% of the other 2193 servers in this category
Published to the registry more recently than 21% of the other 2193 servers in this category
Basic checks equal to or better than 100% of the other 2193 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is memi safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.7.9) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Figma Context MCP

by GLips

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

Runs on your computer★ 16,165MITUpdated 5 months ago

Install

Claude Real Video

by HUANGCHIHHUNGLeo

Let any LLM watch a video locally — and search everything it has ever watched.

Runs on your computer★ 2,284MITUpdated 2 months ago

Install

Figma MCP Server

by figma

Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.

Runs in the cloud★ 2,152Updated 13 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Memi

The design layer for agentic AI.

Give your coding agent an interface brief before it edits. Memi maps the UI already in your repository, surfaces file-anchored accessibility and design-system risks, and gives you a deterministic check to rerun before merge. Start with the CLI, then add the same gate to every pull request.

Memi Studio is available today; Memi Canvas is currently in development. No account, API key, Figma file, global install, or daemon is required for the first audit.

Start with your next interface · Get Memi Studio · Read the research

Quickstart: find your first interface issue

Run one non-destructive audit in any frontend repository. It needs no account, API key, Figma file, global install, or daemon.

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

The result carries normalized finding IDs, confidence, provenance, and file:line evidence so an agent can act on a specific finding instead of guessing.

Give the same context to your coding agent:

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

Then ask:

Audit this frontend before editing it. Prioritize the five changes that will matter most to users, reuse the existing system, and verify the result after the patch.

If Memi catches a real interface issue in your project, share the finding. Real reports are the most useful signal for what to improve next.

Cost and offline operation

Local source diagnosis uses deterministic rules: no model call, API key, or model fee. It checks the repository you provide and returns findings your agent can verify. Installation, CPU time, CI runners, and any agent you choose still have costs. The published research has not established an end-to-end dollar or token savings advantage.

Start with one diagnosis, address the highest-confidence finding, and rerun the same check. Use --agent-context for a bounded file index instead of sending a whole repository to a model. Its routing is heuristic; a smaller context is not proof of a cheaper successful task. --files scopes reported findings without launching Git; it still scans the tree for aggregate statistics.

Published beta: Install the exact 2.8.0-beta.2 package for the 2.8 frontend workflow. Stable remains 2.7.9; the beta is not a stable release. See current release state and known limitations.

The beta2 npm release record identifies its published source and immutable artifact evidence. The beta1 npm release record preserves the earlier release's history; it does not validate beta2. The 2.8 locked default and explicit capability contract do not apply retroactively to 2.7.9.

npx -y @memi-design/cli@2.8.0-beta.2 --version

npx -y @memi-design/cli@2.8.0-beta.2 agent brief . --frontend --intent "Improve this interface" --json

The beta keeps managed security review, SwiftUI parity, and full DesignWorkbench certification explicitly pending. It is not stable or employer-approved. Publication provenance and platform receipts belong to the exact released artifact.

The beta prevents local diagnosis from writing project files by default, keeps paid integrations optional, and requires explicit grants for networking, subprocesses, and source report persistence. An npm install needs registry access; offline first-run claims require the separately verified bundle. See the acceptance ledger, known limitations, and release truth.

The 2.8 frontend workflow: the beta provides a repository-aware frontend brief, four useful locked MCP tools, validated Figma/Paper evidence inputs, and explicit component-reuse conflicts. See the frontend workflow for runnable beta commands and the release plan for remaining gates. Managed independent security scanning and the reviewed-candidate-audit and swiftui-rendered-rerun receipts remain pending for stable. Paper pixel parity is unassessed. Of 158 inventoried CLI paths, 105 remain deferred; broad grants do not enable them. No complete-task dollar or token savings claim is established.

What 2.8 changes for frontend agents

In 2.7.9	In the 2.8 beta
Diagnosis, agent briefs, token tools, Figma bridge, and skills already existed.	`agent brief --frontend` joins actual exports, props, CSS/DTCG tokens, and CSF stories in a 2–16 KiB JSON response.
Harness configuration exposed a broad tool catalog.	Locked stdio starts without sockets or project writes; four read tools are available without grants.
A design mapping could become stale or a generator warning could be ignored.	Explicit mappings are checked against current exports, required props, token references, and optional source hashes. Registry specs marked as mapped block duplicate generation; a host envelope supplies reuse guidance.
Paper had no dedicated integration.	Codex can supply selected Paper or Figma context through the same validated envelope; no extra model session or bundled connector is required.
Static diagnosis could present unassessed categories as passing.	Quality scores cover assessed categories only; coverage and scan omissions are separate. Browser verification remains unassessed until actually run.

The practical benefit is more useful local evidence and clearer failure signals: a brief identifies an existing component before an agent duplicates it, diagnosis distinguishes unchecked categories from assessed findings, and diagnose --receipt-only provides a separate metadata-only result without persisting a source report. Regression tests also exposed and corrected candidate defects in bounded file reads, malformed event handling, and failure exit codes. Those corrections improve specific behavior; they do not establish universal design quality, security certification, or lower task cost.

Earlier packed results at source 2a6d0e44 are historical evidence for those exact bytes. Later defensive runtime fixes supersede that artifact as a release candidate; each corrected source checkpoint is verified through a separate local package and digest. See the verification record for the source, artifact, and scope of each result. Local candidate receipts remain evidence for their original bytes; they do not replace the published npm record.

The repository remains authoritative for code. Memi supplies evidence; Codex edits and runs the project's actual checks. Existing custom CSS and component systems do not need a shadcn migration. This beta deliberately defers many legacy command paths; it is not yet a drop-in upgrade for every 2.7 workflow.

Put the check on every pull request

Copy examples/github-actions/memi-design.yml into your repository as .github/workflows/memi-design.yml. The starter is pinned to the reviewed public Action commit and gives reviewers:

a PR check that fails only on newly introduced interface debt;
a memi-design-health artifact with the human-readable report; and
SARIF annotations when the repository grants security-events: write.

The workflow does not need an API key or a Memi secret. Fork pull requests still receive the check and report; SARIF upload is skipped automatically when GitHub does not grant that permission.

If you prefer to configure it by hand, the complete GitHub Action guide documents every input, output, permission, and evidence file.

One product layer, three surfaces

Surface	What it is	Status
Memi CLI	Interface intelligence and deterministic checks for local repositories, agents, and CI.	Available today
Memi Studio	A macOS workbench for bringing project context, agent workflows, and verification together.	Available today
Memi Canvas	A visual workspace for design-system context and controlled agent proposals.	currently in development

See the product

Memi Studio	Memi Canvas — in development

Bring an agent prompt, project memory, and a verification surface into one workbench.	Preview design-system context, inspect a proposal, and keep a human in the loop. This preview shows an active development build, not a released product guarantee.

What Memi adds to an agent workflow

Before the edit	During the edit	Before merge
Discover components, tokens, routes, states, and accessibility gaps.	Give the agent a scoped brief that names the system it must preserve.	Rerun deterministic checks and surface new interface debt in CI.

Need	Start with
Find UI risks and product-system context	`audit-frontend-design`
Plan a change around existing components and tokens	`remember-design-system`
Keep new interface debt out of pull requests	`enforce-design-ci`
Build and verify native Apple interfaces	`build-swiftui-interface`

Compatible with the shadcn registry and v0 design systems.

Evidence at a glance

The V15 confirmatory audit is a public technical disclosure, not a leaderboard. It separates receipt admission, rendered design quality, functional acceptance, and resource observations.

Measured record	Exact reading
36 / 36 frozen receipts admitted	Every preregistered agent cell had an auditable receipt. This is receipt admission, not universal performance.

| 10 complete model-graded matched pairs | Rendered design-quality comparisons that survived the

Only the beginning is shown; read the rest in the repo

memi

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Design, images & audioi

Common questions

Alternatives

Figma Context MCP

Claude Real Video

Figma MCP Server

README from the maker

Memi

Quickstart: find your first interface issue

Cost and offline operation

What 2.8 changes for frontend agents

Put the check on every pull request

One product layer, three surfaces

See the product

What Memi adds to an agent workflow

Evidence at a glance