mxLore
Reduces context-switching and knowledge loss by maintaining a persistent, searchable codebase history that AI assistants can reference across sessions.
Self-hosted MCP server for AI coding assistants. Persistent knowledge base with 39 tools, 11 skills, institutional memory.
- Auto-complete architectural decisions based on prior project patterns
- Generate code stubs matching team conventions stored in knowledge base
- Retrieve context for legacy system refactoring without manual onboarding
Reduces context-switching and knowledge loss by maintaining a persistent, searchable codebase history that AI assistants can reference across sessions. Eliminates the need to re-explain architecture, past decisions, or project context for each interaction.
Engineering teams building internal tools or maintaining proprietary codebases who want AI assistants to understand project-specific patterns, past implementations, and institutional knowledge without external cloud dependency.
https://github.com/MicrotronX/mxLore
By MicrotronX
How to Get It
claude plugins install MicrotronX/mxLore
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me auto-complete architectural decisions based on prior project patterns
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 29 GitHub stars; 1 contributors; last commit 10d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 29 GitHub stars; 1 contributors; last commit 10d ago; license no license.