Codebase Knowledge Graph MCP Server
Related Servers
Alternatives to Codebase Knowledge Graph MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceCombines a knowledge graph with RAG (Retrieval-Augmented Generation) capabilities for semantic code indexing and search. Enables creating entity relationships, managing observations, and performing semantic searches across indexed codebases.13-
- AlicenseAqualityDmaintenanceEnables creating and querying semantic knowledge graphs to model business logic, code relationships, and project structure across multiple projects.111MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a local, versioned knowledge graph of a software project, retrieving overviews, context packs, evidence, and explanations to make informed changes.MIT
- AlicenseAqualityDmaintenanceEnables AI to analyze, query, and manage a graph-based representation of software architecture for impact analysis, dependency tracking, and design.205 npm1AGPL 3.0
- FlicenseNot gradedqualityAmaintenanceEnables developer agents to perform semantic codebase search, dependency and impact analysis, cross-file refactoring, and full-stack API tracing through a unified query DSL over a high-performance graph engine.-
- AlicenseBqualityAmaintenanceEnables tracing code entities through requirements to strategic goals, surfacing orphan code and allowing query of intent via graph primitives like orphans, trace, and corpus.19MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: creating, deleting, or querying entities, relations, or observations. No overlap between tools like create_entities and create_relations, or delete_entities and delete_observations.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_entities, delete_relations, search_nodes). No deviations or mixed conventions.
With 9 tools, the server covers the essential operations for a knowledge graph: CRUD for entities, relations, and observations, plus graph-wide and search queries. The count is well-scoped without bloat.
The tool set provides create, read (via open_nodes, read_graph, search_nodes), and delete operations for all core elements. The update aspect is partially covered by add_observations and create_relations, but missing explicit update for entity or relation properties, which is a minor gap.