The failure it targets is specific: two files with zero imports between them that must change together, which no type checker and no test suite will flag. Git history knows about it, and this puts that knowledge in front of the agent before it writes code. Three tools is a small surface, and the licence is noncommercial — check that before putting it on work machines.
An MCP server that mines git history and test files to surface the context an agent cannot see in the code it was handed. It answers "what usually changes when this file changes", extracts the intent strings from the tests that cover it, and keeps a persistent store of notes so an insight from one session reaches the next one.
- A blast-radius report for one file — coupled files with a risk level and score, the commit ratio behind it, plus any stored notes and test intents — `get_impact_analysis`
- A note attached to a file that automatically appears in every future impact analysis — `save_project_note`
- Saved notes searched by content or file path, or listed whole — `read_project_notes`
- Test intent strings pulled from Vitest, Jest, Mocha, Playwright and Cypress; JUnit 4 and 5, Kotest and ScalaTest; native Rust `#[test]`; Pytest and Unittest; and native Go `func Test...`
- An adaptive index that switches to path-filtered mode on large repositories — targets are under 2 seconds on a first run and under 200ms after that
No account and no key — everything runs on your hardware and the project states zero telemetry. Install with `claude mcp add --scope user --transport stdio engram -- npx -y @spectra-g/engram-adapter`, or point any client at `npx -y @spectra-g/engram-adapter`; the published version is 0.2.11 over stdio. It stores its index in `.engram/engram.db` beside the repository. Building from source needs Rust 1.70+ and Node.js 18+. Licensed PolyForm Noncommercial 1.0.0 — free for personal and non-profit use, commercial use requires a separate license.
One command — npx -y @spectra-g/engram-adapter