cc-sensei
Related Servers
Alternatives to cc-sensei
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude Code and AI coding agents to retrieve compact, task-shaped code evidence bundles via MCP, combining AST-aware retrieval, hybrid BM25+FAISS search, call-graph traversal, reranking, and token-budgeted context assembly.1MIT
- 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
- AlicenseAqualityDmaintenanceAn MCP server that gives Claude structural understanding of a codebase—dependency graph, entry points, complexity ranking, and import cycles—without reading every file into context.4MIT
- AlicenseNot gradedqualityDmaintenancePersistent codebase knowledge layer for AI agents. Pre-digests codebases into structured knowledge (symbols, dependency graphs, co-change patterns, architectural decisions) and serves via MCP. 28 languages, 14 tools, ~85% token reduction.29 npm10MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to retain facts, decisions, and lessons across sessions through local semantic search, and to automatically detect, classify, and trend user corrections as behavioral patterns. It also runs reflection cycles that promote or retire learned frameworks, all through 15 MCP tools and hooks with no cloud dependency.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to index codebases into a queryable knowledge model and ask for the smallest architectural surface a task likely touches, with evidence, confidence, and freshness, via MCP tools.Apache 2.0
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: listing modules, getting module content, searching architecture knowledge, searching patterns, tracing concerns, and reading source code. No two tools overlap significantly, and descriptions clarify any potential ambiguity.
All tools follow a consistent verb_noun pattern (e.g., get_module, list_modules, trace_concern) with clear, descriptive verbs. No mixing of conventions.
Six tools is well-scoped for an architectural knowledge base, providing essential operations without being overwhelming. Each tool serves a necessary role.
The tool surface covers all major activities: discovering modules (list_modules), retrieving module details (get_module, get_source_code), searching across the knowledge base (query_architecture, trace_concern), and accessing design patterns (search_patterns). No obvious gaps for a read-only reference server.