Codebase Memory vs ctxlint
Codebase Memory is an open-source MCP server for knowledge and memory. ctxlint is an open-source MCP server for developer tools.
- Codebase Memory is best for find callers of a function.
- ctxlint is best for audit context files before a pr.
- What it is
- Codebase Memory is an open-source MCP server for knowledge and memory.ctxlint is an open-source MCP server for developer tools.
- Best for
- Find callers of a functionAudit context files before a PR
- Kind
- MCP serverMCP server
- Pricing
- Open sourceOpen source
- Platforms
- CLI, macOS, Linux, Windows, self-hostedCLI
- Runs
- LocallyLocally
- GitHub stars
- 48.7K
- Last commit
- Nov 2026
- License
- MIT
- Open source
- Good for
- Find callers of a function; Assess the impact of a diff; Link documentation to codeAudit context files before a PR; Catch a leaked key in .mcp.json; Trim context bloat
What Codebase Memory does
Code knowledge graph
Persistent graph of symbols, calls and dependencies.
Multiple search modes
Structural, full-text and local semantic search.
Documentation links
Indexes Markdown, reStructuredText, AsciiDoc and ADRs.
Infrastructure tracing
Connects Docker, Kubernetes, Terraform and CI to source.
Change impact
Maps a diff to affected symbols and related tests.
Native CLI
Query the same graph from the command line.
What ctxlint does
Broken-path detection
Suggests fixes from git history.
Command checks
Compares commands with scripts and targets.
Secret scan
Flags keys in tracked configs.
Token budget
Shows context cost per file.
Contradiction finder
Spots conflicting instructions.
Sibling-repo drift
Compares secrets and workflows.
Codebase Memory vs ctxlint: questions
Is Codebase Memory or ctxlint cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Codebase Memory and ctxlint?
Codebase Memory is an open-source MCP server for knowledge and memory. ctxlint is an open-source MCP server for developer tools.
