Codebase Memory vs GitFlic MCP
Codebase Memory is an open-source MCP server for knowledge and memory. GitFlic MCP is an open-source MCP server for developer tools.
- Codebase Memory is best for find callers of a function.
- GitFlic MCP is best for review merge requests from an agent.
- What it is
- Codebase Memory is an open-source MCP server for knowledge and memory.GitFlic MCP is an open-source MCP server for developer tools.
- Best for
- Find callers of a functionReview merge requests from an agent
- Kind
- MCP serverMCP server
- Pricing
- Open sourceOpen source
- Platforms
- CLI, macOS, Linux, Windows, self-hostedCLI, self-hosted
- 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 codeReview merge requests from an agent; Triage issues on GitFlic; Cut a release
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 GitFlic MCP does
78 CLI-mapped tools
Each tool maps to one gitflic subcommand.
Read-only mode
Expose no mutating tools.
Tool groups
Keep only chosen groups to save context.
No-destructive switch
Remove deletion tools.
Project resolver
Detects the project from the git remote.
Codebase Memory vs GitFlic MCP: questions
Is Codebase Memory or GitFlic MCP cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Codebase Memory and GitFlic MCP?
Codebase Memory is an open-source MCP server for knowledge and memory. GitFlic MCP is an open-source MCP server for developer tools.
