A
licenseNot graded
qualityA
maintenanceEnables AI coding agents to persist and retrieve project knowledge using three MCP tools with local vector and full-text search.
MIT
Lore Agent
by zfy465914233
Related Servers
Alternatives to Lore Agent
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to retrieve and manage code context with hybrid search, project memory, and observability via MCP tools.29MIT
- AlicenseBqualityAmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.77383 PyPI71MIT
- AlicenseNot gradedqualityDmaintenanceA local-first personal AI agent infrastructure that extends Claude Desktop with tools for Google services, web scraping, local memory, knowledge upload, and dynamic workflows via MCP.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve token-budgeted project context, search code symbols, look up definitions, and access project memory and cross-project learnings through local MCP tools. It reduces redundant exploration by supplying the smallest useful context from a deterministic, local-first index.MIT
TDQS
A4.2/5.0
Scored across 12 tools
Disambiguation4/5
Most tools have distinct purposes (query, save, ingest, validate, fetch, list, lint, scan, build, import). However, save_research, capture_answer, and ingest_source all persist knowledge cards with different input formats, which could cause confusion despite detailed descriptions.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case (e.g., query_knowledge, save_research, fetch_url). Verbs are descriptive and the pattern is predictable across all 12 tools.
Tool Count5/5
12 tools is well-scoped for a knowledge management server. The set covers querying, saving, ingesting, validating, listing, linting, scanning dead links, building graphs, and importing notes—no bloat or deficiency.
Completeness3/5
The tool surface covers create (save, capture, ingest), read (query, list), and checking tools, but lacks update and delete operations for knowledge cards. This is a notable gap that could hinder full life cycle management.
Maintenance
ActivityInactive
ResponsivenessNo issues