mimry
Related Servers
Alternatives to mimry
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to maintain persistent memory across repositories by indexing local files into a semantic graph and providing ranked, verified search results without LLM token costs.3 npmMIT
- AlicenseAqualityBmaintenanceSelf-hosted semantic code search for AI coding agents. Indexes many repositories at once with tree-sitter AST chunking, local llama.cpp embeddings and Qdrant, so Claude Code, Cursor, Codex and any MCP client can find code by meaning, trace usages and callers, and read the git history behind each chunk. No API keys, and your code never leaves your machine.21811MIT
- AlicenseNot gradedqualityCmaintenanceGives multiple AI coding agents a shared, persistent memory by indexing your code and documentation into a vector database with AST-aware chunking and hybrid semantic/keyword search. Agents can search across projects and store, update, or forget decisions, conventions and lessons learned, all self-hosted with local embeddings.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to query a local semantic code graph for surgical context, cross-file resolution, framework-aware routes, and code intelligence while keeping indexes automatically up to date.77,341 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding assistants persistent project memory and semantic code search, running fully locally with no API keys required.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI coding tools to query a local index of documents, code, and crawled web pages using hybrid keyword and semantic search with re-ranking, plus knowledge graph, memory, and agent workflow tools. It also lets clients trigger source syncing and ingestion so context stays current.-
TDQS
Scored across 9 tools
Most tools have distinct purposes (impact=change effects, path=relationship route, why=ranking explanation, feedback=telemetry), but there is mild overlap between mimry_preflight and mimry_status (both readiness/state checks) and between mimry_find and mimry_related (both return files for a query). The descriptions largely disambiguate these, but an agent could still hesitate on which readiness or file-retrieval call to pick.
All tools share a uniform mimry_ prefix and single lowercase word style, which is predictable and readable. However the words mix nouns (impact, path, status, symbol) and verbs (find, why, feedback), so it is consistent in form but not a strict verb_noun pattern.
Nine tools is well-scoped for a code-graph/search server, with each tool covering a distinct facet (search, symbols, relationships, impact, status, feedback). No filler or redundant entries.
The surface covers search, symbol lookup, graph relationships, change impact, ranking explanation, and readiness/freshness well. The one notable gap is a dedicated index build/reindex operation, since status/preflight only report freshness rather than triggering indexing.