dnomia-knowledge
Related Servers
Alternatives to dnomia-knowledge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides Claude Code with local semantic search and indexing of your codebase using AST-aware chunking and hybrid search, enabling deep code understanding without sending data to the cloud.MIT
- FlicenseNot gradedqualityDmaintenanceA high-precision local knowledge base server enabling AI agents to navigate, search, and reason about complex codebases using hybrid semantic, lexical, and graph retrieval.3-
- FlicenseNot gradedqualityBmaintenanceProvides hybrid semantic and keyword code search for Claude Code using BM25 and vector retrieval. It enables indexing and searching local codebases with language-aware chunking and local embeddings.-
- AlicenseNot gradedqualityAmaintenanceEnables persistent, searchable memory for Claude Code by storing session knowledge in a local PostgreSQL + pgvector database, with hybrid vector and full-text search, automatic session mining, and knowledge graph curation.MIT
- AlicenseNot gradedqualityCmaintenanceA local, persistent, semantically-aware knowledge graph for AI coding agents like Claude Code, providing efficient session memory with minimal token cost and zero runtime network calls.MIT
- AlicenseNot gradedqualityBmaintenanceProvides Claude with persistent, semantic knowledge of a codebase across sessions by maintaining a local knowledge base of structural maps, compressed file summaries, and insights.7 npm1MIT
TDQS
Scored across 7 tools
Each tool targets a clearly distinct function: project listing, search, local indexing, graph traversal, file reading, URL ingestion, and lifecycle management. There is no meaningful overlap in purpose even though some tools touch related data.
Tool names mix conventions: index_project and read_file are verb_noun, project_info and graph_query are noun_verb, search is a bare verb, and lifecycle is a noun only. While all names are readable and snake_case, there is no predictable pattern across the set.
Seven tools is a well-scoped size for a knowledge management server, covering indexing, retrieval, graph exploration, and state management without unnecessary redundancy. Each tool earns its place.
The core knowledge lifecycle is covered: ingestion via index_project/fetch_and_index, retrieval via search/read_file, graph access, and state changes via lifecycle. A notable gap is the absence of any deletion/removal tool for projects, chunks, or indexed content.