A
licenseNot graded
qualityC
maintenanceAn AI memory system that creates isolated, persistent memory banks for each codebase, solving the context-switching problem by keeping project knowledge separate and accessible across sessions.
7
5
MIT
Kratos-MCP
by FoggyStorm
Related Servers
Alternatives to Kratos-MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides a structured documentation system for context preservation in AI assistant environments, helping users create and manage memory banks for their projects.377MIT
- AlicenseBqualityCmaintenanceProvides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.16612MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to maintain persistent project context across sessions by storing and retrieving structured information in markdown files organized in a memory bank directory.457Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides persistent memory and semantic code understanding for AI assistants using MongoDB Atlas Vector Search. Enables intelligent code search, memory management, and pattern detection across codebases with complete semantic context preservation.1513MIT
- AlicenseBqualityDmaintenanceGives AI coding assistants persistent memory, safety controls, and project awareness by tracking coding sessions, protecting critical files from modifications, and managing approval workflows with automatic changelog generation.196MIT
TDQS
B3.2/5.0
Scored across 27 tools
Disambiguation4/5
Most tools have distinct purposes with clear resource-action pairs, such as concept_get vs. concept_search or memory_save vs. memory_search. However, some tools like security_encrypt and security_scan could be confused for overlapping security functions, and context_preview vs. context_rules_get might cause minor ambiguity in context management.
Naming Consistency5/5
The tool names follow a highly consistent verb_noun pattern throughout, with clear prefixes like concept_, context_, memory_, prd_, project_, prompt_, security_, and system_. All tools use snake_case uniformly, making them predictable and easy to parse for agents.
Tool Count3/5
With 27 tools, the count is borderline high for a single server, suggesting potential over-scoping. While the tools cover multiple domains (concepts, context, memory, PRD, projects, prompts, security, system), this many tools might overwhelm agents or indicate fragmentation rather than a cohesive set.
Completeness4/5
The tool set provides comprehensive coverage across key domains like concept management, memory handling, project operations, and security, with clear CRUD-like operations. Minor gaps exist, such as no direct tool for deleting concepts or updating memories, but agents can likely work around these with available tools like memory_forget or concept_save.