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-read331MIT
- 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.1,612 npm77MIT
- 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.23Apache 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,198 npm183MIT
- 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 have clearly distinct purposes, but search_graph and search_code both perform search (symbol vs text) and query_graph vs trace_path both involve graph traversal, which could cause misselection. Descriptions help differentiate them, but a couple of pairs remain potentially confusing.
Tool names mostly follow a snake_case verb_noun pattern (get_architecture, index_repository, search_graph, delete_project). Minor deviations exist: index_status is ambiguous (verb vs noun) and manage_adr is vague, but overall the pattern is predictable.
17 tools is slightly above the ideal 3-15 range, but each tool has a specific role in codebase indexing, querying, and analysis. The count feels a bit heavy but not excessive given the domain breadth.
The surface covers core workflows: indexing, searching, querying, tracing, snippet retrieval, architecture overview, project management, and diff detection. Minor gaps exist, such as ingest_traces not implementing edge creation and no direct file listing tool, but most operations can be completed or worked around.