Knowledge MCP
Related Servers
Alternatives to Knowledge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that builds a semantic graph memory from a project directory, indexing documentation and code into graph structures and exposing 70+ MCP tools for search, knowledge management, task management, and more.9 npm15Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server for intelligent memory and task management with semantic search, automatic task extraction, and knowledge graphs, enabling AI assistants to maintain context and learn project conventions.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that builds a knowledge graph from code and text documents, enabling Q\&A and implementation planning via tools like graph_create, graph_plan, and graph_query.7MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server providing persistent memory for AI coding assistants by storing and searching architectural decisions, patterns, and solutions. It also includes tools for git automation and mapping codebase expertise based on project history.MIT
- AlicenseNot gradedqualityAmaintenancePersistent memory MCP server that remembers decisions and context across coding sessions, automatically logging and surfacing relevant knowledge as you work.36 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that provides persistent project context, workflow management, and knowledge capture for AI coding agents. It enables agents to maintain structured memory across sessions by tracking project profiles, conventions, skills, and technical debt.7-
TDQS
Scored across 5 tools
The tools are mostly distinct: search/context are read-only queries (with context being more natural-language free-form), start_task/finish_task are lifecycle hooks, and remember is the only write operation. The main ambiguity is between search and context, which both retrieve project knowledge, though descriptions differentiate them reasonably.
Tool names follow a clean snake_case verb pattern (search, context, remember, start_task, finish_task). However, they mix verbs and nouns inconsistently - two are bare verbs (context, remember, search) while two are verb_noun compound tasks (start_task, finish_task). The naming is readable but not patterned.
Five tools is ideal for a knowledge-management MCP server. Each tool maps to a clear function: querying (search/context), task lifecycle (start/finish), and writing (remember). There's no bloat or redundancy in the count.
The surface covers the full knowledge-management lifecycle: read (search/context), write (remember), and contextual hooks (start/finish_task). A minor gap is the absence of an explicit delete/update operation for knowledge records - forget or edit are missing - but the core workflow is well covered.