Manual setup required. The maintainer's config contains paths only you know - edit the placeholders below before adding it to Claude Code.
1
Prepare the server locally
Run this once before adding it to Claude Code.
npm install -g lore-mcp2
Register it in Claude Code
claude mcp add lore-mcp -- node /path/to/lore-mcp/dist/index.jsReplace any placeholder paths in the command with the real path on your machine.
3
Make your agent remember this setup
lore-mcp's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- Automatically extracts architectural decisions from project files
- Detects security gaps like unprotected routes and missing auth middleware
- Analyzes git history for bug-fix ratios and high churn files
- Captures the 'why' behind technical decisions via CLI
- Provides a diagnostic doctor command for setup issues
Try it
→Analyze my project and extract the architectural decisions made so far.
→Check my codebase for potential security gaps or unprotected routes.
→Record a new decision: 'We chose PostgreSQL over MongoDB because we need ACID transactions for payments.'
→Show me the current status of my project's architectural decisions by category.
→Run a diagnostic check on my project setup to identify any issues.
Original README from EliotShift/lore-mcp
<h1 align="center">LORE — Architectural Memory for AI Coding</h1>
<em>AI forgets why your code was built this way. LORE remembers.</em>
See it in action
Why LORE?
Every time you open Claude Code or Cursor, it starts with zero context.
Without LORE, you manually explain every session:
- "We use PostgreSQL because we need ACID transactions"
- "JWT expiry is 24h due to mobile requirements"
- "4 of our API routes have no auth middleware"
With LORE, one command gives AI full context automatically:
npx lore-mcp init
Quick Start
npm install -g lore-mcp
cd your-project
lore init
lore status
What LORE detects
| Source | What it finds |
|---|---|
package.json |
Databases, frameworks, auth, security libs |
| Source code | Unprotected routes, error handling %, MVC patterns |
| Git history | Bug-fix ratio, high churn files, commit quality |
| Manual input | WHY behind decisions via lore decide |
CLI
lore init # Analyze project → extract 24 decisions
lore status # View all decisions by category
lore decide "reason" # Record WHY behind a decision
lore doctor # Diagnose setup issues
lore --version # Show version
Capture the WHY
Automated extraction finds WHAT. lore decide captures WHY:
lore decide "chose PostgreSQL over MongoDB — need ACID for payments"
lore decide "rejected Redis sessions — JWT scales better for microservices"
lore decide "helmet enabled — security audit requirement Q1 2026"
MCP Integration
Add to Claude Code / Cursor settings:
{
"mcpServers": {
"lore": {
"command": "node",
"args": ["/path/to/lore-mcp/dist/index.js"]
}
}
}
What LORE finds in a real project
SECURITY
● bcrypt for password hashing
● Helmet.js for HTTP security headers
● 3 of 5 routes may lack auth middleware ← security gap
● JWT secrets must be in environment variables
RISK
● High bug-fix ratio: 3/5 recent commits are fixes
● Low commit message quality: 0%
● High churn file: src/services/userService.ts
Built by
@TheEliotShift — Developer from Morocco 🇲🇦
If LORE saved you time → ⭐