codebase-memory-mcp
★ 47.7k
vs
gortex
★ 1.9k
codebase-memory-mcp vs gortex
codebase-memory-mcp: codebase-memory-mcp is a structural analysis backend that indexes codebases into a persistent knowledge graph, drastically reducing token usage for code exploration by providing precise structural results. It integrates with AI assistants like Claude Code, offering advanced capabilities such as call graph tracing, architecture overviews, and dead code detection.; gortex: Gortex is a code intelligence engine that builds an in-memory knowledge graph of repositories. It provides CLI, MCP Server, and web UI for querying symbols, dependencies, and impact analysis. Designed for AI coding agents, it cuts token usage by ~94% by replacing multiple file reads with a single smart_context call.
Editorial Head-to-Head Analysis
Both build a code knowledge graph for coding agents. Codebase Memory is MIT with a single binary and a stated focus on token savings. Gortex lists more MCP tools (49) and multi-repo workspaces, but GitHub does not detect its licence, so confirm the terms first.
01
TL;DR
codebase-memory-mcpMemory & Context · ★ 47.7k
When to choose:
- Your agent burns tokens searching a medium or large codebase: one graph query replaces many grep and read steps, according to the README.
- You want everything local: a single static binary with no runtime dependencies or API keys.
- You work in many languages and with several coding agents, which the installer configures automatically.
When to skip:
- You do not want an installer to edit your agents' config files and add hooks; the README offers --skip-config to install only the binary.
- You need project decisions and conventions rather than code structure; a scaffold such as mex is closer.
- You are cautious about unsigned binaries: some antivirus engines have flagged the release, which the project documents as a false positive.
gortexCode Assistant · ★ 1.9k
When to choose:
- You work across several repositories and want cross-repo symbol resolution in one graph.
- You want a wide set of analysis tools: the README lists blast radius, dead code, hotspots, rename and test-coverage gaps among its 49 MCP tools.
- You want a CLI, an MCP server and a web UI over the same graph, covering 92 languages.
When to skip:
- You need clear licence terms today: GitHub does not detect a licence, so confirm the terms before using it at work.
- You are on Windows: the README lists Windows support as planned.
- You want a small tool surface; the README is very long and the tool set is large.
02
Side-by-Side Comparison
Field
codebase-memory-mcpgortexCategory
Memory & Context
Code Assistant
Stars
★ 47.7k
★ 1.9k
License
MIT
NOASSERTION
Install Command
curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash
OS=$(uname -s | tr '[:upper:]' '[:lower:]') && ARCH=$(uname -m) && case $ARCH in x86_64) ARCH=amd64 ;; aarch64|arm64) ARCH=arm64 ;; esac && curl -LO "https://github.com/zzet/gortex/releases/latest/download/gortex_${OS}_${ARCH}.tar.gz" && tar -xzf "gortex_${OS}_${ARCH}.tar.gz" && sudo mv gortex /usr/local/bin/
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
knowledge-graph, codebase-analysis, AI-assistant-tools
ai-tools, antigravity, claude-code
03
Features
codebase-memory-mcp01Indexes a codebase into a persistent knowledge graph using tree-sitter, with semantic type resolution for several major languages
02Supports 150+ languages with grammars compiled into a single static binary
0317 MCP tools: search, call tracing, architecture overview, impact analysis, dead code detection, Cypher queries and more
04Indexes infrastructure-as-code such as Dockerfiles and Kubernetes manifests
05Built-in 3D graph visualisation served locally
gortex01Knowledge graph of files, symbols, imports, call chains, and type relationships
02Multi-repo workspaces with cross-repo symbol resolution and scoping
0392 languages support via tree-sitter and regex extractors
0449 MCP tools for symbol lookup, analysis, scaffolding, and agent feedback
05Semantic search with hybrid BM25 + vector search and RRF fusion
04
Use Cases
codebase-memory-mcp↳Code exploration and understanding: Quickly understand codebase architecture, find functions, and trace call paths without high token costs.
↳Impact analysis and refactoring: Map git diffs to affected symbols, detect dead code, and analyze function fan-out to aid refactoring efforts.
↳AI assistant integration: Enhance AI assistants like Claude Code with precise structural queries for more effective code-related questions.
↳Architecture Decision Records management: Store, update, and retrieve architectural decisions directly within the codebase context.
↳Automated scripting and CI/CD: Utilize CLI mode for single-shot graph operations in scripts or CI/CD pipelines.
gortex↳Integrate with AI coding agents as a context engine to reduce token usage
↳Multi-repository impact analysis and cross-repo refactoring
↳Semantic code search and codebase understanding for developers
05
Best For
codebase-memory-mcpMost Popular
gortexTrending
FAQ
FAQ
What is the difference between codebase-memory-mcp and gortex?
Both build a code knowledge graph for coding agents. Codebase Memory is MIT with a single binary and a stated focus on token savings. Gortex lists more MCP tools (49) and multi-repo workspaces, but GitHub does not detect its licence, so confirm the terms first.
Which is better, codebase-memory-mcp or gortex?
The best choice depends on your use case. Choose codebase-memory-mcp if Code exploration and understanding: Quickly understand codebase architecture, find functions, and trace call paths without high token costs., and gortex if Integrate with AI coding agents as a context engine to reduce token usage.
Is codebase-memory-mcp free or open source?
Yes, codebase-memory-mcp is open source on GitHub (MIT).
Is gortex free or open source?
Yes, gortex is open source on GitHub (NOASSERTION).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→