Self-hosted knowledge server for AI coding agents. 45 MCP tools, institutional memory, skill evolution. Works with claude.ai, Claude Code, Cursor, Windsurf, and any MCP client.
latest Build 113 — one-click Self-Update from the Admin UI, server-side write-safety guard, dev-login & 4-level ACL.Every AI coding session starts from zero. Your decisions, your specs, your lessons — gone.
Shared knowledge that survives context switches. Each team runs their own server — one developer can work across multiple teams seamlessly. Stop re-explaining architecture to your AI.
Architectural decisions tracked and enforced — from a chat window. Open claude.ai, ask “What did my team decide last week?” and get instant answers. No terminal needed. Data-driven skill evolution.
Write specs, review decisions, track progress — all from claude.ai. No terminal, no CLI. Everything you create is instantly available to your development team’s AI agents.
Self-hosted, GDPR-compliant, audit-ready. Your code knowledge never leaves your infrastructure. Full access logs and revision history.
Not a toy. Not a demo. 45 production tools forged through months of daily use across real projects.
.mxbundle file. AES-256-GCM via Windows CNG + PBKDF2 key-derivation. 5-step wizard in the Admin UI covers conflict resolution, developer re-mapping, and audit.application/problem+json surfaces every reason — no more stale keys silently failing in production.Each project connects to its own mxLore server through a dedicated proxy. Teams stay autonomous — different databases, different API keys, different knowledge. One developer can seamlessly work across all of them.
Per-team server. One developer switches context automatically via per-project proxy.
Client A's knowledge never leaks into Client B. Full isolation, one laptop.
Department-level silos by design. Cross-team sharing via opt-in project relations.
From flat files to full knowledge management.
| Capability | CLAUDE.md | Memory MCP | mxLore |
|---|---|---|---|
| Persistent knowledge | File only | Key-value | Structured DB |
| Cross-project search | No | No | Full-text + relations |
| Multi-developer | No | No | ACL + per-dev keys |
| Decision tracking (ADRs) | Manual | No | First-class doc type |
| Skill evolution | No | No | Auto-tuning + metrics |
| Institutional memory | No | Basic | Recall + gate levels |
| Session orchestration | No | No | Workflows + team agents |
| AI batch maintenance | No | No | 12 boot-time jobs |
| Admin UI | No | No | Tabbed dashboard, INI editor, intelligence |
| Encrypted project migration | Plain JSON or none | Plain JSON or none | AES-256-GCM .mxbundle + PBKDF2 |
| API key lifecycle | No lifecycle, manual | No lifecycle, manual | Rotation, expiry warnings, grace, revoke |
| RFC 7807 error format | Opaque 500 | Opaque 500 | application/problem+json on 5xx |
| Multi-server / Multi-team | No | No | Per-project server |
| Works in chat UI (claude.ai) | No | No | Full MCP access |
| Self-hosted | Local file | Varies | Your server |
code or chat
Your CTO reviews decisions in chat. Your developer codes with full context. Same memory, different window.
Review decisions from a chat window. No terminal needed.
Code with full context from yesterday’s discussions.
Separate client knowledge bases, one chat window for all.
Every number from actual deployment. No inflated benchmarks.
One command. Five skills. Zero manual steps.
From zero to institutional memory. No JSON editing, no config wikis.
localhost:8081 → new member → copy API key/mxSetup. Paste your API key.# 1. Download the setup skill (one-liner) mkdir -p ~/.claude/skills/mxSetup curl -o ~/.claude/skills/mxSetup/SKILL.md https://raw.githubusercontent.com/MicrotronX/mxLore-skills/main/mxSetup/SKILL.md # 2. Open the Admin UI in your browser — this is where the API key lives # http://localhost:8081 (first start has no login) # Click "New member" → enter a name → copy the generated mxk_... key # 3. Back in Claude Code: run mxSetup with that key /mxSetup mxk_your_api_key_here # mxSetup asks: Server URL? → http://localhost:8080/mcp # Downloads skills from GitHub, installs proxy, configures MCP # Done in ~15 seconds. 45 tools ready.
# No CLI. No terminal. Just chat. # 1. Get an API key — two ways: # (a) You host mxLore yourself → open http://localhost:8081 # → click "New member" → copy the generated mxk_... key # (b) Someone else hosts it → ask your team admin for a key # 2. Open claude.ai → Settings → Integrations → Add MCP Server Name: mxLore Server URL: http://your-server:8080/mcp Auth Header: Authorization: Bearer mxk_your_api_key # 3. Done. All 45 MCP tools available in any chat. # Try it: you: "Search my project knowledge about authentication" # → Claude automatically uses mx_search you: "Create a new spec for payment redesign" # → Claude creates the doc via mx_create_doc # Note: Skills (/mxOrchestrate, /mxPlan etc.) are Claude Code only. # claude.ai gets all 45 MCP tools directly.
# Start your session — orchestrator loads context automatically /mxOrchestrate resume # Plan a feature — spec, plan, and decisions tracked in DB /mxPlan "Add user authentication with OAuth2" # AI recalls relevant decisions automatically you: "How did we handle token refresh last time?" # → mx_recall finds ADR-0042 + 3 related lessons # Review your code — skills learn from your feedback /mxDesignChecker /mxBugChecker # Save everything — session notes, state, lessons extracted /mxSave
One-time purchase. All features. All updates. Forever yours.
Source available · Server: BSL 1.1 (converts to Apache 2.0) · Skills: MIT · Full details →
Deploy in minutes. 15-second onboarding. Your infrastructure, your data, your rules.