Skip to content
MCP SERVER

Interface understanding as MCP tools

memi exposes design evidence, audits, briefs, tokens, and spec-first scaffolds through MCP so coding agents can ask for product UI context before they write.

REGISTRY

Public install target

Registry idio.github.sarveshsea/memi
Package@memi-design/cli@2.5.0
ModeWorks code-first with --no-figma; Figma context is optional.
REMOTE

Connect over Streamable HTTP

MCP SERVER URL
https://www.memoire.cv/api/mcp
  • memi_capabilities - discover remote and local execution boundaries.
  • prepare_design_agent_brief - generate a compact, executable design workflow.
  • get_design_ci_policy - create deterministic UI quality gates.
  • get_install_instructions - configure npm, MCP, Agent Skills, and agent kits.
  • get_public_proof - resolve canonical package, registry, docs, and proof links.

The remote server is stateless and read-only. Repository files, write-approved scaffolds, local audits, and Figma context stay in the npm MCP server so Memi never pretends Vercel has access to a caller's project.

START

Run the full engine locally

TERMINAL
npm i -g @memi-design/cli@2.5.0
memi mcp start --no-figma
MCP CONFIG
{
  "mcpServers": {
    "memoire": {
      "command": "memi",
      "args": ["mcp", "start", "--no-figma"]
    }
  }
}
TOOLS

v2.5.0 agent design tools

  • prepare_design_agent_brief - compact, standard, or full design-agent summaries.
  • scaffold_agent_design_files - dry-run or approved Atomic Design spec scaffolds.
  • run_audit - local design, UX, and craft evidence for a repo or route.
  • design_doc - agent-ready interface summaries from a live route.
  • get_tokens - token context without forcing Figma connection.
Codex pluginSkillsDesign CI