Memoire MCP server
io.github.sarveshsea/memoire·v0.16.1·50 starsShadcn-native Design CI for Tailwind apps with registry export and MCP UI tools.
50 stars131 downloads/wk
Reviews
Write oneNobody has reviewed Memoire yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Memoire tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-11 · same rubric, same numbers if you re-run it
- Code scan412 source files scanned10/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 7 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (3)
- mediumnpm install lifecycle script present
install.script - mediumeval / new Function used
exec.evaldist/mcp/tools.js: … { pattern: /\beval\s*\(/, reason: "eval() is not allowed inside figma_execute" }… - mediumnpm install lifecycle script present
install.scriptpackage.json: …epare": "node scripts/prepare.mjs", "postinstall": "node scripts/postinstall.mjs" }, "…
How Memoire compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 71/100
- higher than 33% of 1,113 Developer tools servers
- GitHub stars
- 50
- more than 91% of 857 Developer tools servers
- Downloads a week
- 131
- more than 63% of 510 Developer tools servers with a package
Install Memoire in Claude Code, Cursor or VS Code
Runs npx -y @sarveshsea/memoire on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add memoire -- npx -y @sarveshsea/memoire
What the publisher says
From the Memoire repository's README, as published. We do not edit it. Read it on GitHub
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 noneThe 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-designThen 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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Memoire: common questions
- Is Memoire MCP server safe?
- Mostly: it is graded B (71/100). Read the Memoire safety report
- How do I install Memoire?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Memoire need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Memoire maintained?
- The last commit was 11 days ago (2026-11-04). The latest release is v0.16.1.
- What can I use instead of Memoire?
- Servers from other publishers that do the same job: Git MCP server, Metaplex Agent Registry MCP server and Observatory MCP server.
- How does Memoire compare with other Developer tools MCP servers?
- safety score 71/100 (higher than 33% of 1,113 Developer tools servers); github stars 50 (more than 91% of 857 Developer tools servers); downloads a week 131 (more than 63% of 510 Developer tools servers with a package). Full comparison.
Alternatives to Memoire
Same job from other publishers: the closest match first, then the best rated.
- GitComprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.not reviewedEstablishedA
- Metaplex Agent RegistryDeploy AI agents on-chain on Solana with an EIP-8004 identity. Deploy fee funds $THREE buybacks.not reviewedEstablishedB
- ObservatoryMCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.not reviewedEstablishedB
Aiven MCPProvision PostgreSQL, manage Apache Kafka, and deploy apps with Aiven - all from your AI assistant.not reviewedEstablishedA- Advanced GitLab MCP server66 tools, 242 typed actions, 27 registry groupsnot reviewedGrowingA