| FMRS | 63 / 100 · C | 79 / 100 · B |
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 11 / 20 | 18 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
| Best for | - AI coding-agent users who need local code-structure analysis
- Development teams seeking to reduce file-by-file search and context-token usage
- Projects requiring cross-file, cross-package, or cross-repository relationship queries
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
| Not for | - Users who require a built-in LLM or natural-language-to-graph-query translation
- Environments where the server must not read local source code
- Scenarios that require only a remote cloud service instead of a local stdio process
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
| Required permissions | - Read access to local repositories and related configuration files being indexed
- Write access to ~/.cache/codebase-memory-mcp/ for persistent indexes and logs
- The installer may write agent configuration, instructions, skills, and lifecycle hooks
- The optional UI may serve a local interface at localhost:9749
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
| Risks and side effects | - Indexing and searching process local source code, so its scope and cache location should be reviewed
- The installer modifies agent configuration, skills, instructions, or hooks
- Uninstall and project deletion can remove associated configuration or graph data; deletion requires confirmation
- Although the source describes signatures, checksums, and antivirus scanning, users should still audit binaries before execution
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
| Supported clients | Claude Code, Codex, Gemini CLI, Zed, OpenCode, Cursor, Windsurf, Aider, KiloCode, VS Code, GitHub Copilot CLI, OpenHands, Cline, Qwen Code, Factory Droid, Goose, Mistral Vibe, Qoder CLI, Kimi Code CLI, Rovo Dev CLI | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
| Tools | 14 | 0 |