mcp-kb-server
Related Servers
Alternatives to mcp-kb-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides knowledge graph-based persistent memory for LLMs, allowing them to store, retrieve, and reason about information across multiple conversations and sessions.9152,087 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides persistent memory and conversation continuity for Claude Desktop and Claude Code, allowing users to save and restore project context when threads hit token limits.MIT
- AlicenseBqualityFmaintenanceA Model Context Protocol server for AI agents to manage tasks and track progress across projects, with features like project isolation, search, and reporting.115 npm1MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server providing AI assistants with comprehensive project, task, and subtask management capabilities with project-specific storage.2920 npm88MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that provides persistent memory capabilities for AI systems, enabling true continuity of consciousness across conversations through episodic, semantic, procedural, and strategic memory types.246-

Lspace MCP Serverofficial
FlicenseAqualityFmaintenanceAn open-source server implementing the Model Context Protocol (MCP) that enables capturing insights from AI sessions and transforming them into persistent, searchable knowledge accessible across tools.78-
TDQS
Scored across 25 tools
Each tool targets a distinct subsystem (wiki, memory, KB, source, summary, dashboard) and operation. Despite 25 tools, descriptions clearly differentiate them; no two tools appear to perform the same function, and domain prefixes (wiki., memory., kb., etc.) aid disambiguation.
All tools follow a consistent 'noun.verb' pattern (e.g., memory.store, kb.search, source.ingest, summary.project). The naming uses dot-separated domain prefixes and action suffixes uniformly, making the pattern predictable and easy to navigate.
With 25 tools, the count is at the high end of the 'borderline' range (16-25 felt heavy). While the tools are organized across multiple subsystems, the overall surface area is large and could be trimmed to reduce cognitive load, though it remains functionally justifiable.
The server provides good coverage for memory and KB (full CRUD plus index/search), but the source subsystem lacks update and delete operations, and the wiki subsystem only offers lint/export/link without direct create/read/update/delete. These gaps hinder full lifecycle management for those domains.