codebase-memory-mcp vs graphify
Code knowledge graphs for coding assistants compared
codebase-memory-mcp and graphify turn project files into knowledge graphs that coding assistants can query to explore code and relationships. codebase-memory-mcp focuses on local code indexing through an MCP server, while graphify also extracts information from documents and other media and offers CLI and assistant-skill workflows.
codebase-memory-mcp: Build a Searchable Code Knowledge Graph
A local MCP server that indexes repositories into a persistent graph of code structure and relationships. It helps AI coding agents answer architectural and code-navigation questions with focused queries instead of repeated file searches.
graphify: Turn Codebases into Queryable Knowledge Graphs
Graphify builds a queryable knowledge graph from code, documentation, schemas, and other project files. It helps developers and AI coding assistants explore relationships, trace paths, and understand codebases without relying on a vector store.
| codebase-memory-mcp | graphify | |
|---|---|---|
| Language | C | Python |
| License | MIT | Apache-2.0 |
| Stars | 45.7k | 124k |
| Forks | 3.8k | 11.9k |
| Last analyzed | Oct 3, 2026 | Oct 3, 2026 |
Key differences
- codebase-memory-mcp stores its graph locally in SQLite and supports automatic change detection and re-indexing; graphify generates a graph visualization, Markdown report, and reusable JSON graph.
- codebase-memory-mcp offers structural, semantic, and full-text search alongside graph queries; graphify focuses on graph exploration and is not a vector-search index.
- codebase-memory-mcp indexes code structure and can include Dockerfiles and Kubernetes resources; graphify can also include documents, media, SQL schemas, and configuration files.
- codebase-memory-mcp is written in C and licensed under MIT; graphify is written in Python and licensed under Apache-2.0.
- codebase-memory-mcp runs as a local MCP server or one-shot CLI; graphify is a Python CLI and assistant skill that can also expose queries through MCP.
- The supplied project facts list 45.7k stars for codebase-memory-mcp and 124k for graphify; both are marked as not archived.
Choose codebase-memory-mcp if you…
- need a local MCP server with persistent SQLite graph storage and automatic re-indexing.
- want structural, semantic, and full-text search together with call tracing or change-impact analysis.
- need to explore routes and calls across services or inspect Dockerfiles and Kubernetes resources.
Choose graphify if you…
- want to include documentation, PDFs, media, schemas, or configuration files in a project graph.
- need graph visualizations, Markdown reports, and JSON output for reuse.
- want extracted and inferred relationships labeled separately, or prefer a Python CLI and assistant-skill workflow.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.