LumenCore MCP Server

Local setup required. This server has to be cloned and prepared on your machine before you register it in Claude Code.
1

Set the server up locally

Run this once to clone and prepare the server before adding it to Claude Code.

Run in terminal
npm install -g lumencore
2

Register it in Claude Code

After the local setup is done, run this command to point Claude Code at the built server.

Run in terminal
claude mcp add lumencore -- node "<FULL_PATH_TO_LUMENCORE>/dist/index.js"

Replace <FULL_PATH_TO_LUMENCORE>/dist/index.js with the actual folder you prepared in step 1.

README.md

Persistent project memory for AI agents.

LumenCore

Persistent project memory for AI agents.

LumenCore is a local Model Context Protocol (MCP) server that gives AI coding assistants like Claude Code persistent memory across sessions. It solves the problem of context loss when conversations reset, allowing agents to retain architectural decisions, code patterns, domain knowledge, and project history.

The Problem

AI coding assistants lose all context when a session ends. Every new conversation starts from scratch, requiring you to re-explain:

  • Architectural decisions and their rationale
  • Code conventions and patterns used in the project
  • Domain-specific concepts and terminology
  • Previous work and ongoing tasks

The Solution

LumenCore provides a local memory layer that AI agents can read from and write to. When Claude Code connects to LumenCore, it can:

  • Remember important decisions, patterns, and concepts
  • Recall relevant context using full-text search
  • Activate automatically at session start to load project knowledge

All data stays local on your machine in a SQLite database.

Installation

npm install -g lumencore

Quick Start

# 1. Add LumenCore to Claude Code (once per machine)
claude mcp add lumencore -- lumencore serve

# 2. Initialize in your project
cd /your/project
lumencore init

# 3. Start Claude - LumenCore activates automatically
claude

What `lumencore init` Does

The init command sets up everything for seamless integration:

  1. Creates/updates CLAUDE.md - Instructs Claude to activate LumenCore at conversation start
  2. Configures permissions - Auto-allows all LumenCore tools (no permission prompts)
  3. Scans your project - Captures structure, tech stack, and key files

CLI Commands

lumencore init      # Initialize LumenCore in current project
lumencore setup     # Run the global setup wizard
lumencore serve     # Start the MCP server (used by Claude Code)
lumencore status    # Show configuration and memory stats
lumencore export    # Export memories to JSON for backup/migration
lumencore version   # Show installed version
lumencore reset     # Clear all data (use --force to confirm)
lumencore help      # Show help

Export Options

lumencore export             # Export current project memories
lumencore export --global    # Export global memories only
lumencore export --all       # Export all memories
lumencore export -o backup.json  # Custom output file

Tools Available to Claude

Once connected, Claude Code can use these tools:

`lumencore_activate`

Called automatically at session start. Loads project context and scans new projects.

`remember`

Store important project knowledge.

Parameters:
- category: "decision" | "pattern" | "concept" | "note" | "task"
- title: Short description
- content: Full details
- tags: Optional categorization tags
- importance: 1-5 (default 3)

Example prompt:

"Remember that we decided to use Redux Toolkit for state management because it reduces boilerplate."

`recall`

Search stored memories using full-text search.

Parameters:
- query: Search terms
- category: Filter by type (optional)
- limit: Max results (default 10)

Example prompt:

"Recall any decisions about state management."

`list_memories`

Browse all stored memories for the current project.

`forget`

Delete a memory by ID.

Memory Categories

Category Use For
decision Architectural choices and their rationale
pattern Code conventions, naming patterns, common approaches
concept Domain knowledge, business logic, terminology
note General observations and learnings
task Work items, TODOs, progress tracking

How It Works

┌─────────────────┐     MCP Protocol      ┌─────────────────┐
│   Claude Code   │ ◄──────────────────► │   LumenCore     │
└─────────────────┘                       │   MCP Server    │
                                          ├─────────────────┤
                                          │  Memory Service │
                                          ├─────────────────┤
                                          │  SQLite + FTS5  │
                                          └─────────────────┘
  1. Claude Code connects to LumenCore via the MCP protocol
  2. At session start, Claude calls lumencore_activate to load project context
  3. During the session, Claude uses remember to store important discoveries
  4. Claude uses recall to search for relevant knowledge when needed
  5. Memories persist in SQLite with full-text search indexing

Configuration

Run lumencore setup to configure:

  1. Memory scope: Project-only (isolated) or project + global (shared knowledge)
  2. Data directory: Where to store SQLite databases

Config is stored at:

  • Linux: ~/.config/lumencore/config.json
  • macOS: ~/Library/Preferences/lumencore/config.json
  • Windows: `%APPDATA

Tools (5)

lumencore_activateLoads project context and scans new projects at session start.
rememberStore important project knowledge like decisions, patterns, or tasks.
recallSearch stored memories using full-text search.
list_memoriesBrowse all stored memories for the current project.
forgetDelete a memory by ID.

Configuration

claude_desktop_config.json
{"mcpServers": {"lumencore": {"command": "lumencore", "args": ["serve"]}}}

Try it

Remember that we decided to use Redux Toolkit for state management because it reduces boilerplate.
Recall any decisions about state management.
List all architectural patterns I have saved for this project.
Remember this task: Refactor the authentication module to use the new API client.
Recall notes related to the database schema.

Frequently Asked Questions

What are the key features of LumenCore?

Persistent memory across AI coding sessions. Full-text search for project knowledge retrieval. Categorized memory storage (decisions, patterns, concepts, notes, tasks). Local-only data storage using SQLite. Automatic session activation and project scanning.

What can I use LumenCore for?

Retaining architectural decisions and their rationale across long-term projects. Storing project-specific code conventions and naming patterns for consistent development. Tracking ongoing tasks and TODOs within the AI agent's context. Documenting domain-specific terminology and business logic for easier onboarding.

How do I install LumenCore?

Install LumenCore by running: npm install -g lumencore

What MCP clients work with LumenCore?

LumenCore works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep LumenCore docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.
Open Conare