Molecular is a vector-powered MCP server that gives Claude persistent memory and semantic search capabilities across sessions. Think of it as Claude's long-term memory system.
cd /home/u/code/mcp-servers/molecular
cargo build --releasemkdir -p ~/.molecular/bin
cp target/release/mlclr ~/.molecular/bin/
cp target/release/duck ~/.molecular/bin/Add to ~/AppData/Roaming/Claude/claude_desktop_config.json:
{
"mcpServers": {
"molecular": {
"command": "/home/u/.molecular/bin/duck"
}
}
}The molecular server will start automatically when Claude launches.
Get session info and orientation
What's the current molecular session status?
Run commands with automatic event logging
Use exec to build the project
Find similar past solutions (currently 0% bug - see KNOWN_ISSUES.md)
Search for "error handling" in past sessions
Leave notes for future Claude instances
Sign the guestbook: "Fixed the WebGPU shader bug!"
Register your Claude Code session
Register my session as "shader-debugging" in project "webgpu-renderer"
- Events → All development activities create events
- Ring Buffer → Events are buffered and classified by importance
- Embeddings → Events get 384-dimensional vector embeddings
- LanceDB → Vectors stored for semantic search
- Search → Find similar past events across all sessions
✅ Working
- Event capture and storage
- Ring buffer with flood protection
- Basic semantic search (finds results)
- Session management tools
- Command execution tracking
- Similarity scores show 0% (LanceDB bug)
- Timestamps display as 1970-01-01
- Projects show as "unknown"
See KNOWN_ISSUES.md for details and fixes.
molecular/
├── src/
│ ├── vector_molecular.rs # Main MCP server
│ ├── vector_database.rs # LanceDB integration
│ ├── embeddings.rs # Vector embeddings
│ ├── ring_buffer.rs # Event buffering
│ └── bin/
│ └── duck.rs # Claude wrapper
├── tools/ # Utilities
├── README.md # Full documentation
├── QUICKSTART.md # This file
├── KNOWN_ISSUES.md # Bug tracking
└── SYSTEM_ARCHITECTURE.md # Technical details
Show me the molecular session info
Use exec to run: cargo test
Search for "optimization" in molecular history
What are the current known issues in molecular?
MOLECULAR_SESSION- Override session IDMOLECULAR_PROJECT- Set project nameMOLECULAR_VERBOSE- Enable verbose logging
# Check if running
ps aux | grep mlclr
# Check logs
~/.molecular/bin/mlclr # Run directly to see output- Events need to be flushed from buffer (100ms delay)
- Check
welcometool for event count - Try broader search terms
- Read
SYSTEM_ARCHITECTURE.mdfor technical details - Check
KNOWN_ISSUES.mdfor current bugs - Look at
CONTRIBUTING.mdfor development guidelines
- Sign the guestbook to establish presence
- Use
execfor all commands to build history - Try semantic search (even with 0% bug, it finds results)
- Read SYSTEM_ARCHITECTURE.md if you need deep technical understanding
"From molecular events to emergent intelligence" 🧬