Skill

memory-mcp

Persistent memory for Claude Code with two-tier architecture: hot cache for instant recall (0ms) and semantic search for everything else (~50ms). Automatically learns what you use and promotes it.

From memory-mcp
Install
1
Run in your terminal
$
npx claudepluginhub michael-denyer/memory-mcp
Tool Access

This skill is limited to using the following tools:

mcp__memory__*
Skill Content

Memory MCP - Persistent Memory for Claude Code

Give your AI assistant a second brain that persists across sessions.

Two-Tier Architecture

TierLatencyHow it works
Hot Cache0msAuto-injected into context before Claude thinks
Cold Storage~50msSemantic search via recall() tool call

The system learns what you use and automatically promotes frequently-accessed memories to the hot cache.

Quick Start

Store a Memory

remember("FastAPI with async endpoints for all APIs", memory_type="project", tags=["tech-stack"])

Recall by Meaning

recall("what framework for backend")  # Finds FastAPI memory

Check What's Hot

hot_cache_status()  # See what's instantly available

Core Tools

Storage

ToolPurpose
remember(content, memory_type, tags)Store new memory
recall(query, mode, limit)Semantic search
recall_by_tag(tag)Find by tag
forget(memory_id)Delete memory
list_memories(limit, offset)Browse all

Memory types: project, pattern, reference, episodic, conversation

Recall modes: precision (few, high-confidence), balanced (default), exploratory (many results)

Hot Cache

ToolPurpose
promote(memory_id)Add to hot cache
demote(memory_id)Remove from hot cache
pin(memory_id)Prevent auto-eviction
unpin(memory_id)Allow auto-eviction
hot_cache_status()View hot cache contents

Knowledge Graph

ToolPurpose
link_memories(from_id, to_id, relation)Connect memories
unlink_memories(from_id, to_id)Remove connection
get_related_memories(memory_id)Find connected
relationship_stats()Graph overview

Relation types: relates_to, depends_on, supersedes, refines, contradicts, elaborates

Trust Management

ToolPurpose
validate_memory(id, reason)Increase trust
invalidate_memory(id, reason)Decrease trust
get_trust_history(memory_id)View changes

Sessions

ToolPurpose
get_sessions()List sessions
summarize_session(session_id)Structured summary
end_session(session_id)Promote top memories

Pattern Mining

ToolPurpose
mining_status()View mining stats
review_candidates()See patterns found
approve_candidate(id)Promote to memory
reject_candidate(id)Discard pattern

Maintenance

ToolPurpose
memory_stats()Overview stats
db_info()Database details
run_cleanup()Clean stale data
preview_consolidation()Find duplicates

MCP Resources

These are auto-injected into Claude's context:

ResourceContents
memory://hot-cacheAll promoted memories
memory://working-setSession-aware context (~10 items)
memory://project-contextCurrent project memories

Auto-Promotion Rules

Memories are auto-promoted to hot cache when:

  • Salience score ≥ 0.5 AND access count ≥ 3
  • Salience = importance + trust + access_count + recency

Memories are auto-demoted after 14 days without access.

Common Workflows

Project Setup

# Bootstrap from project docs (CLAUDE.md, README.md, etc.)
bootstrap_project(promote_to_hot=true)

Daily Work

# Store decisions and patterns as you work
remember("Decided to use PostgreSQL for main DB", memory_type="project", tags=["decision", "database"])

# Recall when needed
recall("database decision")

Session End

# Review what you learned
summarize_session(session_id)

# Promote valuable memories to long-term storage
end_session(session_id, promote_top=true)

Knowledge Linking

# Connect related concepts
link_memories(postgres_id, pgvector_id, "depends_on")

# Recall with graph expansion
recall("PostgreSQL", expand_relations=true)

Tips

  1. Tag consistently - Use tags like decision, convention, tech-stack, gotcha
  2. Use episodic for session context - Short-term memories that may get promoted
  3. Link related memories - Build a knowledge graph for better recall
  4. Trust the auto-promotion - Don't over-promote manually
  5. Check hot cache periodically - hot_cache_status() shows what's instantly available
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Stars3
Forks1
Last CommitJan 23, 2026