Memory for Coding Assistants

Your AI coding assistant forgets your project between sessions. Fix it with persistent memory.

The Problem

You told Claude Code your deploy target is Railway. Tomorrow it suggests Heroku. You explained the database schema last week. Today it asks again. Every session is Groundhog Day.

The Solution

One line — and your coding assistant remembers everything across sessions, projects, and tools.

claude mcp add mnemoverse \
  -e MNEMOVERSE_API_KEY=mk_live_YOUR_KEY \
  -- npx @mnemoverse/mcp-memory-server

For detailed setup per tool, see the integration guides:

• Claude Code & Desktop
• Cursor, VS Code & Windsurf

Or give your agent this URL to self-configure: https://raw.githubusercontent.com/mnemoverse/.github/main/llms.txt

What Gets Remembered

Your coding assistant will proactively remember:

Category	Example
Project setup	"Uses PostgreSQL + Prisma, deployed on Railway"
Preferences	"Always use pnpm", "Prefers Tailwind over CSS modules"
Decisions	"Chose REST over GraphQL for caching simplicity"
Lessons	"Never deploy on Fridays — learned the hard way"
People	"Alice owns the design system, Bob reviews API changes"
Patterns	"Exponential backoff fixed timeout issues in this service"

Cross-Tool Memory

Write a memory in Claude Code → read it in Cursor. The same API key works everywhere.

Monday in Claude Code:
  You: "We always use feature branches, never push to main directly"
  Claude: [stores memory]

Wednesday in Cursor:
  You: "Push this change"
  Cursor: [reads memory] "Created feature branch. PR to main as usual."

Recommended CLAUDE.md Setup

Add this to your project's CLAUDE.md to make Claude use memory proactively:

## Memory

This project uses Mnemoverse for persistent memory across sessions.

**Before answering** questions about preferences, past decisions, project 
setup, or anything discussed previously — call `memory_read` first.

**After learning** something worth keeping (preference, decision, lesson,
project fact) — call `memory_write` to store it.

Don't rely only on local memory files — Mnemoverse memory is shared across 
all AI tools and team members.

Team Memory

Same API key for the whole team → shared institutional knowledge:

• New team member's AI already knows the project conventions
• Decisions made in one person's session are available to everyone
• Onboarding happens automatically through accumulated memory

For isolation: use domain: "user:{name}" for personal preferences, domain: "project:{name}" for shared context.

Get Started

1. Get an API key (free, 30 seconds)
2. Pick your tool: Claude | Editors | ChatGPT
3. Add the CLAUDE.md snippet to your project
4. Start coding — memory builds automatically