OpenLMlib
Allows ingesting session activity from git history to automatically build memory without manual logging.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpenLMlibsearch for findings about contextual chunking"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OpenLMlib
Local knowledge and research library for LLM workflows
Store, retrieve, and collaborate on findings with semantic search, full-text search, and multi-agent collaboration sessions.
๐ Full Documentation ยท Quickstart ยท MCP Tools ยท CollabSessions
Features
Knowledge Base: SQLite metadata + JSON findings + FAISS/Numpy vector index
Semantic Retrieval: Multi-phase retrieval with semantic + lexical search, deduplication, and reranking
MCP Server: 76 tools for AI assistants (17 core + 11 memory + 48 collaboration)
CollabSessions: Multi-agent collaboration with message passing, artifacts, and templates
Co-Scientist Workflow: Linked hypothesis generation and independent verification sessions
CLI: Full command-line interface for management and diagnostics
Portable: Findings exportable as JSON, easy backup and restore
Related MCP server: memento
Quickstart
Installation
npm install -g openlmlib
openlmlib setup # Interactive wizard with React TUIOther options:
pipx (Python only)
pipx install openlmlib
openlmlib setupFrom Source
git clone https://github.com/Vedant9500/LMlib.git
cd LMlib
pip install -e .
openlmlib setupNote: The embedding model (~100-500MB) downloads during
setup, not installation.
First Steps
# Check health
openlmlib doctor
# Add a finding
openlmlib add \
--project myproj \
--claim "Contextual chunking improves retrieval by 15-30%" \
--confidence 0.85 \
--evidence "https://arxiv.org/example" \
--reasoning "Benchmarks show context-aware chunking outperforms fixed-size"
# Search
openlmlib query "retrieval techniques" --final-k 5
# List findings
openlmlib list --limit 20Configure AI Assistants
# Interactive setup (recommended)
openlmlib setup
# Or configure specific IDEs
openlmlib mcp-config --ide vscode --ide cursor
# Codex CLI / Claude Code
openlmlib mcp-config --ide codex_cli --ide claude_codeEach MCP client needs its own config entry. A custom prompt in Antigravity can
encourage OpenLMlib usage there, but Codex or Claude will not see the MCP until
openlmlib is registered in their MCP config and the client is restarted or
refreshed.
MCP startup is optimized for a fast client handshake. The server registers tools first, then starts a delayed runtime/model prewarm in the background so the first semantic retrieval is usually warm by the time you need it. To tune or disable that behavior, set environment variables in the client's OpenLMlib server entry:
[mcp_servers.openlmlib.env]
OPENLMLIB_MCP_PREWARM = "1" # default: 1
OPENLMLIB_MCP_PREWARM_DELAY_SEC = "5" # default: 5
OPENLMLIB_EMBED_PREWARM = "1" # default: 1Set OPENLMLIB_MCP_PREWARM = "0" if you want no background model work. The
main-thread OPENLMLIB_MCP_PREIMPORT_EMBEDDINGS = "1" option is still available
for unusual environments, but it can add 10+ seconds to MCP startup on Windows.
Supported clients: VS Code, Cursor, Claude Desktop, Claude Code, Gemini CLI, Aider, Windsurf, Zed, Cline, and more.
For hypothesis-generation workflows, configure the client first, then ask for a Co-Scientist run or use wording such as "research this and verify the hypotheses". See MCP client integration and system prompt templates.
What Can You Do?
๐ Build a Knowledge Base
Store findings from research, experiments, or analysis with structured metadata:
openlmlib add \
--project retrieval \
--claim "Dynamic chunk sizing reduces hallucination by 20%" \
--confidence 0.78 \
--evidence "https://example.com/study" \
--reasoning "Adaptive chunk size based on query complexity..." \
--caveats "Requires query complexity estimation" \
--tags retrieval,chunking,evaluation๐ Retrieve with Context
Multi-phase retrieval combines semantic similarity, lexical matching, and recency:
# Semantic search with reasoning traces
openlmlib query "contextual retrieval" \
--final-k 5 \
--reasoning-trace
# With filters
openlmlib query "retrieval" \
--project myproj \
--tags retrieval \
--confidence-min 0.8๐ค Use with AI Assistants
76 MCP tools let AI assistants securely access and modify your knowledge base:
Core Tools (17):
init_library,health- Setup and diagnosticssave_finding,delete_finding- Write operations (require confirmation)retrieve_findings,search_findings,search_knowledge- Retrieval and searchlist_findings,get_finding- Browse findingsretrieve_context- Format findings for LLM promptsstart_research,end_session- Composite workflow toolscheck_context,save_finding_auto- Convenience toolsevaluate_retrieval,get_usage_analytics,help_library- Utilities
๐ See all 76 tools โ
๐ฅ Multi-Agent Collaboration
CollabSessions enable structured collaboration between multiple LLM agents:
# Create session from template
openlmlib-mcp --call create_from_template '{
"template_id": "deep_research",
"title": "Research on Retrieval",
"created_by": "gpt-4"
}'
# Join session
openlmlib-mcp --call join_session '{
"session_id": "sess_20260409_abc12345",
"model": "claude-3",
"role": "worker"
}'
# Send and receive messages
openlmlib-mcp --call send_message '{...}'
openlmlib-mcp --call poll_messages '{...}'
# Add artifacts (reports, analysis)
openlmlib-mcp --call save_artifact '{...}'Available Templates:
deep_research- Comprehensive research (5 steps, 5 agents)code_review- Multi-agent code review (5 steps, 4 agents)market_analysis- Market/competitor analysis (4 steps, 4 agents)incident_investigation- Root cause analysis (4 steps, 3 agents)literature_review- Academic literature review (6 steps, 5 agents)co_scientist_generate- Co-Scientist hypothesis generation (6 steps, 7 agents)co_scientist_verify- Co-Scientist independent verification (5 steps, 6 agents)
๐ Full CollabSessions guide โ
๐ง Memory System (Session Persistence & Retrieval)
OpenLMlib includes a powerful memory system that persists session knowledge across work sessions, enabling AI assistants to "remember" what happened in previous sessions and continue work seamlessly.
Key Features:
Session Lifecycle: Start/end sessions with automatic context injection and summarization
Progressive Retrieval: 3-layer disclosure (search index โ timeline โ full details) for token efficiency
Retroactive Ingestion: Auto-ingest session activity from git history โ no manual logging needed!
Caveman Compression: Ultra-compressed context injection (46% token savings)
Memory Tools (11 tools):
session_start - Start session with context from previous sessions
session_end - End session and auto-generate summary
log_observation - Log tool executions for memory building
query_memory - Adaptive memory retriever for relevant observations
search_memory - Layer 1: Search index (~75 tokens/result)
memory_timeline - Layer 2: Chronological context (~200 tokens/result)
get_observations - Layer 3: Full details (~750 tokens/result)
inject_context - Auto-inject relevant context at session start
session_recap - Synthesized recap of recent sessions (~150-250 tokens)
topic_context - Deep dive on specific topics (~500-800 tokens)
ingest_git_history - Auto-ingest from git history (no manual logging!)Example Workflow:
# Start of session - automatically loads relevant context
session_start(
session_id="sess_20260414_001",
query="memory retrieval optimization"
)
# Returns: Context from previous sessions with relevant observations
# During work - observations are logged automatically
log_observation(
session_id="sess_20260414_001",
tool_name="Edit",
tool_input="Modified memory_retriever.py",
tool_output="Added auto_inject_context method"
)
# End of session - auto-generates summary
session_end(session_id="sess_20260414_001")
# Creates synthesized knowledge: files touched, decisions, next steps
# Next session - continue seamlessly
session_recap(limit=3)
# Returns: Structured knowledge from last 3 sessionsToken Efficiency:
Layer 1 only: 75 tokens/result (search index for filtering)
Layer 1+2: 275 tokens/result (timeline context)
Layer 1+2+3: 1,025 tokens/result (full details only for relevant items)
vs. full dump: 3-13x token savings!
Architecture
OpenLMlib
โโโ Knowledge Base
โ โโโ SQLite (metadata, full-text search)
โ โโโ FAISS/Numpy (vector index)
โ โโโ JSON findings (portable, human-readable)
โ
โโโ MCP Server (76 tools)
โ โโโ 17 core library tools
โ โโโ 11 memory tools (session lifecycle, adaptive retrieval, retroactive ingestion)
โ โโโ 48 collaboration tools
โ
โโโ CLI
โ โโโ Setup and configuration
โ โโโ Finding management
โ โโโ Diagnostics (doctor command)
โ
โโโ CollabSessions
โโโ Message bus (SQLite + JSONL)
โโโ Artifact store
โโโ Session templates
โโโ Context compactionDocumentation
๐ Complete documentation is in the docs/ folder:
docs/README.md - Documentation index and quick reference
docs/MCP_TOOLS.md - Complete reference for all 76 MCP tools
docs/COLLAB_SESSIONS.md - Multi-agent collaboration guide
docs/SYSTEM_PROMPT.md - Agent instruction templates
CLI Reference
# Setup and diagnostics
openlmlib setup # First-run bootstrap
openlmlib doctor # Health check
openlmlib --version # Show version
# Knowledge base
openlmlib init # Initialize storage
openlmlib add # Add finding
openlmlib list # List findings
openlmlib get # Get finding details
openlmlib query # Semantic retrieval
openlmlib delete # Delete finding
# Collaboration
openlmlib-mcp # MCP server (auto-configured)
# Backup and restore
openlmlib backup # Create backup
openlmlib restore # Restore from backupConfiguration
Global Install
Settings:
~/.openlmlib/config/settings.jsonData:
~/.openlmlib/data/
Local/Dev Install
Pass
--settings /path/to/settings.json
Uninstallation
# Remove package
npm uninstall -g openlmlib # if installed via npm
pipx uninstall openlmlib # if installed via pipx
pip uninstall openlmlib # if installed from source
# Remove data (optional)
rm -rf ~/.openlmlib # global install data
rm -rf data/ # local install dataDevelopment
git clone https://github.com/Vedant9500/LMlib.git
cd LMlib
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -e ".[dev,faiss]"
# Run tests
python -m unittest discover -s tests -p "test_*.py" -v
# Run MCP server manually
python -m openlmlib.mcp_server --settings ./config/settings.jsonNotes
Vector Search: Uses FAISS if installed, otherwise Numpy fallback
Embedding Model:
BAAI/bge-small-en-v1.5(default; 384-d, best accuracy/speed balance)Python: Requires 3.10+
Global vs Local: Global installs use
~/.openlmlib/, local uses projectdata/
Releases
Versioning: Semantic versioning (MAJOR.MINOR.PATCH)
Changelog: CHANGELOG.md
Release process: RELEASE.md
Contributing
See CONTRIBUTING.md for development workflow and guidelines.
License
MIT License - see LICENSE
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceProvides AI agents with persistent knowledge storage, enabling them to store, search, and retrieve text, documents, and files using semantic and keyword search via MCP tools.32Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides persistent memory for AI coding agents via MCP, enabling agents to store and semantically recall facts, events, and lessons across sessions, all running locally without cloud dependencies.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a local vector memory store for AI agents with semantic search, offline embeddings, and MCP integration, enabling tools like Claude and Cursor to store and retrieve information without cloud dependencies.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to persistently store and semantically search shared knowledge via MCP tools.2MIT
Related MCP Connectors
Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
Shared long-term memory vault for AI agents with 20 MCP tools.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vedant9500/OpenLMlib'
If you have feedback or need assistance with the MCP directory API, please join our Discord server