codebase-memory-mcp
Related Servers
Alternatives to codebase-memory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceInstant codebase knowledge graph MCP server. It auto-detects languages, indexes functions, classes, and call chains, enabling LLMs to navigate code in milliseconds.24MIT
- AlicenseAqualityCmaintenanceCross-repository code knowledge graph MCP server for Java, Kotlin, JavaScript, and TypeScript. Indexes source code into embedded KuzuDB via tree-sitter and exposes 30+ tools for call-flow tracing, multi-hop taint analysis (OWASP/CWE/PCI/STIG), entry-point reachability filtering, performance hotspot detection, and license compliance — without reading source files. 95% fewer tokens vs source-read332MIT
- AlicenseNot gradedqualityAmaintenanceA high-performance code knowledge graph server implementing MCP, indexing codebases into a structured AST knowledge graph with semantic search, call graph traversal, and HTTP route tracing.3,125 npm91MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first code intelligence MCP server that enables coding agents to search code, inspect structure, read exact ranges, and explore Git history with explicit token budgets.146Apache 2.0
- AlicenseAqualityAmaintenanceFramework-aware code intelligence MCP server that builds a cross-language dependency graph from source code. 53 integrations (Laravel, Django, Rails, Spring, NestJS, Next.js, and more) across 68 languages. 100+ tools for navigation, impact analysis, refactoring, security scanning, session memory, and CI/PR reports — up to 97% token reduction.293,723 npm202MIT
- AlicenseNot gradedqualityAmaintenanceA persistent code-intelligence MCP server that builds a queryable knowledge graph of your codebase, enabling AI assistants to perform cross-file structural reasoning, dependency analysis, and blast radius detection.9MIT
TDQS
Scored across 17 tools
Most tools target clearly distinct resources and actions, but search_graph vs search_code and query_graph vs trace_path have overlapping search/traversal semantics that descriptions only partly disambiguate. An agent could still misselect between graph-symbol search and text search, or between generic Cypher traversal and call-path tracing.
All 17 tools use snake_case and follow a mostly verb_noun pattern (search_graph, get_code_snippet, delete_project, check_index_coverage). A few are noun-heavy (index_status, index_repository), but the style is otherwise consistent and predictable.
17 tools is above the typical 3-15 sweet spot and feels heavy for one MCP server, even though the domain is broad. Each tool appears to have a distinct role, but the surface spans indexing, search, graph query, traces, ADR, architecture, and changes, making the set borderline crowded.
Core graph-based codebase lifecycle coverage is strong: indexing, status, coverage, search, snippet retrieval, graph query, tracing, architecture, and project deletion are all present. Minor gaps exist around updating indexed data, managing trace runs, or directly mutating graph content, but there are no obvious critical dead ends for typical analysis workflows.