Memi is the read-only design engineering audit and skill layer for coding agents.
Memi MCP Server (io.github.memi-design/memi)
Memi is the read-only design engineering audit and skill layer for coding agents. This MCP server exposes Memi’s capabilities to developers via an interface suited for model context and tool-driven workflows, with information describing the server as a design audit and skill layer.
🛠️ Key Features
Read-only design engineering audit
Skill layer for coding agents
🚀 Use Cases
Design engineering audit for coding agents
Skill-layer augmentation in coding-agent workflows
⚡ Developer Benefits
Integrates a design audit and skill layer in a model-context setup
⚠️ Limitations
Read-only behavior (no write or modification actions are indicated)
Memi gives coding agents the product context, interface checks, and verification loops they need to ship UI that fits the system already in your repository. Use the CLI and Memi Studio today; Memi Canvas is currently in development. Memi works with Codex, Claude Code, Cursor, MCP clients, and CI.
Run Memi in any frontend repository. The first result is a grounded brief for the next edit: what the product already does, where the relevant UI lives, and what needs verification.
No account, API key, Figma file, global install, or daemon is required. The result carries normalized finding IDs, confidence, provenance, and file:line evidence.
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.
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.
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
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 prespecified screen. This is model-graded evidence, not independent practitioner review.
Buzzr / Expo: mean +1.4; Paraform / web: mean −0.4
The scoped non-inferiority gate passed on both graded task families. It does not establish general superiority.
0 / 21 corrected task-by-resource tests rejected
The study did not establish a speed, cost, or token-use advantage.
Separate historical release record: the 2.7 candidate record reported 2,187 / 2,187 tests passed. It is release evidence, not part of V15 and not proof that every project benefits.
Benchmarks and paper
Quality non-inferiority passed for the scoped Buzzr and Paraform task families. The full paper reports exclusions, failed paths, and limitations without imputation. No superiority, speed, or dollar-savings claim is made. Read the conference-style audit PDF, inspect the protocol and receipts, or review the V17 preregistration.
Memi InterfaceBench v1 is a 100 target tasks specification with 5 pinned seed tasks; it is not an aggregate performance score. The historical candidate record reported 2,187/2,187 tests and 70.57% statements coverage. The greater-than-25% claim remains not verified. Inspect the benchmark contract and workflow evidence.
Memi DesignWorkBench v2 holds 300 task contracts and requires practitioner calibration before any certification claim.
Prompts that map to real workflows
Goal
Copy-paste prompt
Supporting workflow
Establish a baseline before a UI change
Audit this frontend before editing it. Prioritize the five changes with the clearest file:line evidence.
audit-frontend-design
Turn evidence into a scoped plan
Turn the findings into a scoped UI change plan. Reuse existing components and tokens before editing.
remember-design-system
Protect a pull request
Set up a deterministic design CI gate for this pull request. Fail only on newly introduced interface debt and save SARIF plus the HTML report.
enforce-design-ci
Research, stated plainly
The research is disclosure material, not a product leaderboard. It keeps functional, rendered-quality, and resource evidence separate so a result cannot be made to say more than the study supports.
The Action adds code-scanning annotations, a step summary, and a memi-design-health artifact. Existing debt can be baselined while newly introduced debt fails the gate.
Memi has no npm install-time lifecycle scripts, no source upload or covert telemetry, explicit Figma connection, agent-kit --dry-run --json, immutable Action pins, and documented third-party boundaries in NOTICE.
Community
We welcome contributions. See CONTRIBUTING.md for setup and pull-request guidance. Bugs and feature requests belong in issues; questions and real project reports belong in Discussions.
Useful contributions include reproducible audit fixtures, framework adapters, skill improvements, accessible UI cases, motion checks, and before/after reports.
License
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.