| FMRS | 54 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 18 / 20 |
|---|
| Maintenance | 10 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Developers using one of the supported AI coding CLIs, IDEs, or agents
- Teams working with large codebases, logs, web pages, or batch queries
- Users who need work-state recovery after context compaction
| - 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 requiring a dedicated GUI MCP integration not listed as supported
- Users who only need a simple MCP tool and do not want hooks, plugins, or local indexing
- Environments that prohibit local script execution or access to local files, credentials, and network resources
| - 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 | - Requires Node.js, Bun, or another listed runtime to execute locally.
- Sandboxed scripts can read and process local files and can use authenticated CLIs such as gh, aws, gcloud, kubectl, and docker through inherited environment variables and configuration paths.
- ctx_fetch_and_index requires URL fetching; indexed content is stored in SQLite databases under the user's local data directory.
- With hooks or plugins enabled, the server can intercept selected tool calls, record session events, and apply routing rules.
| - 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 | - Tools such as ctx_execute run code supplied by the user or agent; that code may read local files, invoke commands, or use inherited credentials.
- Session and indexed content persist in local SQLite databases; ctx_purge permanently deletes all indexed content.
- Hooks may block or redirect selected tool calls, and routing capabilities vary by client.
- The README's savings percentages are project-reported metrics; actual results depend on tool output and usage.
| - 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, Gemini CLI, VS Code, JetBrains Copilot, GitHub Copilot CLI, Cursor, OpenCode, KiloCode, OpenClaw / Pi Agent, Codex, Kimi Code, Qwen Code, Antigravity IDE, Antigravity CLI, Kiro, Zed, Pi Coding Agent, OMP | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 11 | 0 |
|---|