cortex
Related Servers
Alternatives to cortex
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve token-budgeted project context, search code symbols, look up definitions, and access project memory and cross-project learnings through local MCP tools. It reduces redundant exploration by supplying the smallest useful context from a deterministic, local-first index.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to retrieve and manage code context with hybrid search, project memory, and observability via MCP tools.29MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to save and retrieve code snippets, perform semantic vector search, generate code style guides and wiki documentation, and orchestrate multi-agent workflows through MCP tools.-
- AlicenseNot gradedqualityCmaintenanceProvides AI agents with a governed, three-layer project memory (guide, code facts, and knowledge) through namespaced MCP tools for code search, context compilation, impact analysis, and proposal-driven documentation updates.4 npm2MIT
- FlicenseNot gradedqualityAmaintenanceProvides local-first, cross-session persistent memory that lets AI coding agents store, semantically search, and recall project-specific and cross-project knowledge via MCP tools and resources, with an optional task queue for autonomous execution.-
TDQS
Scored across 10 tools
Most tools target clearly distinct resources and actions: the three memory tools (remember/recall/erase) split cleanly by CRUD verb, snapshots split by create/rewind, and symdex_lookup, sieve_compact, and shield_forecast each have unique purposes. The only mild overlap is between cortex_context_pack and cortex_prompt_lookup, which both operate on token/context handling and could be confused at a glance.
Every tool follows a strict cortex_<namespace>_<action> snake_case pattern (memory_remember, snapshot_create, sieve_compact, etc.). Namespace grouping is predictable and verbs are consistent in style across all ten tools.
Ten tools is well within the ideal 3-15 range and each maps to a distinct capability (memory, code lookup, log compaction, snapshots, safety forecast, context selection). No tool feels redundant or padded.
Memory offers full create/read/delete coverage and snapshots offer create/rewind, so the core lifecycle is present. Minor gaps remain (no snapshot list/prune or memory enumeration), but agents can work around these without dead ends.