Cross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers.
MCPpedia last refreshed this data
io.github.IvenKooLab/loci is an MCP server that cross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 62/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"loci": {
"args": [
"/path/to/loci/mcp_server.py"
],
"command": "python"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Cross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
uvx 'loci-rag' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked loci-rag against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in cloud
Cloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation
Gives AI development tools Firebase-specific capabilities and expertise.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
Draw cloud architecture diagrams with official AWS, Azure and GCP icons from a prompt or Terraform.
MCP Security Weekly
Get CVE alerts and security updates for io.github.IvenKooLab/loci and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
English · 简体中文 · 繁體中文 · 日本語 · 한국어
Turn scattered notes, project docs and agent memories into a knowledge base you can search and ask questions about — as an MCP server, from your terminal, or in the browser.
loci combines vector search with BM25 and returns answers with file > section citations. Your files and index stay on your machine. Embedding and chat requests go to the providers you configure; local endpoints can keep the entire workflow offline.
MCP is the point. Mount loci-mcp in Claude Desktop, Cursor, Cline or any other MCP host and your assistant gets the whole knowledge base as tools. The console and a desktop shell are alternate front-ends to the same index — you never need them.
Quick start · MCP setup · Web console · Usage guide · 中文说明

Actual console UI with fictional demo data. No personal knowledge base, account or API key is connected; counts are illustrative.

| Need | How loci helps |
|---|---|
| Find a decision buried in your notes | Hybrid search across directories, with tag, path and date filters |
| Search for an exact identifier | Literal matching for user_id, api/v2, SHT45 — a symbol does not have to win a semantic ranking |
| Know whether a decision still applies | loci history walks the supersession chain: what replaced it, and when |
| Ask a question and check the evidence | Answers cite source sections; optional claim-by-claim verification |
| Carry context between AI tools | MCP tools share one instance; durable memories are Markdown files |
| See what each coding agent remembers | Harness discovery, file browsing, per-tool stats and digest notes |
| Manage the knowledge base visually | Built-in Web console for search, Q&A, memories, indexing and audit |
| Resume a task exactly where it left off | Structured state by exact key (brain_state_save / brain_state_get) — no ranking in the way |
| Prune memory with evidence instead of vibes | Memory health: citations, corrections and age per note (loci memory-health) |
Markdown, text, HTML, org-mode and chat exports work out of the box. Optional extras add PDF, Word and OCR support. Keep using your existing note editor or Obsidian vault.
Three kinds of "memory" fail differently, and mixing them is the classic misuse:
| Kind | Lives in | Retrieved by | Right for | Wrong for |
|---|---|---|---|---|
| Free-text knowledge | memory notes (brain_remember) | hybrid retrieval | "what do we know about X" | exact resume of a task |
| Structured state | state/<type>/<key>.json (brain_state_save) | exact key, no ranking | ta |