Claude Mem vs Lyro

Side-by-side comparison · Updated May 2026

 
C
Claude Mem
LyroLyro
DescriptionClaude Code is powerful, but it starts every session with a blank slate. You explain your project structure, coding conventions, and past decisions over and over. Claude Mem fixes this by giving Claude Code a persistent memory layer. The plugin works as a lightweight MCP server that Claude Code connects to automatically. When you tell Claude something important — a naming convention, an architectural decision, a bug fix rationale — you can save it to memory with a simple command. On the next session, Claude Code loads those memories as context before it starts working. Memories are stored as structured files in your project directory. Each memory has a category (architecture, convention, decision, bugfix, todo) and a relevance scope (project-wide or directory-specific). This structure means Claude Code loads only relevant memories, keeping the context window clean. The plugin ships with automatic memory extraction too. When Claude Code finishes a task, Claude Mem can prompt it to save key learnings. This creates a growing knowledge base that gets smarter over time. After a week of use, Claude Code knows your project's patterns, your team's style, and your past debugging sessions. Installation takes about two minutes. Clone the repo, add it to your Claude Code MCP settings, and restart. No database to set up, no API keys to configure. Everything lives in your project's .claude-mem directory, which you can commit to git for team sharing. Claude Mem is free and open source. It works with any Claude Code setup — free tier, Pro, or Max. The memory format is plain Markdown, so you can read and edit memories directly if you want more control.Tidio's Lyro page provides comprehensive details about the use of cookies on their website. It outlines the purpose of cookies, categorized by their function such as Necessary, Preferences, Statistics, and Marketing. Specific necessary cookies used by various services, from Cookiebot to Google and Hubspot, are described, along with their purposes, expiry times, and types. This information ensures transparency and gives users control over their cookie consent preferences.
CategoryDeveloperApplicationLegal
RatingNo reviewsNo reviews
PricingFreePricing unavailable
Starting PriceFreeN/A
Plans
  • FreeFree
Use Cases
  • Developers using Claude Code daily
  • Development teams
  • Solo developers
  • New team members
  • Web Admins
  • Digital Marketers
  • Data Analysts
  • Privacy Advocates
Tags
claude-code-pluginpersistent-memorycontext-managementmcp-serverdeveloper-tools
cookie policytransparencycookie consentnecessary cookiespreferences
Features
Persistent memory storage across Claude Code sessions with no re-explanation needed
Structured memory categories: architecture, convention, decision, bugfix, todo
Scoped relevance — project-wide or directory-specific memory loading
Automatic memory extraction prompts after task completion
Plain Markdown memory format that is human-readable and editable
MCP server integration — connects to Claude Code in two minutes
Git-friendly storage in .claude-mem directory for team sharing
Zero configuration — no database, no API keys, no external dependencies
Works with all Claude Code tiers: free, Pro, and Max
Growing knowledge base that accumulates project intelligence over time
Detailed cookie descriptions
Necessary cookies listed by service
Expiry and type specified
Multiple consent categories: Necessary, Preferences, Statistics, Marketing
Manage cookie preferences
Transparency in cookie usage
Compliance with CCPA
Variety of cookies from various services
Optimal website performance
User experience improvement with cookies
 View Claude MemView Lyro

Modify This Comparison