get_impact_analysisLABSCO SUMMARY
Catches the coupling that has no import to follow.
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.
What it is
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.
What you get
- 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 Gofunc 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
Requirements
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.
Setup effort
One command — npx -y @spectra-g/engram-adapter
USE CASES
01
Not breaking the thing nobody imports
Run the impact check on the file you are about to edit and read whatever comes back flagged Critical before touching anything.
02
Keeping a hard-won discovery from evaporating
Write the non-obvious constraint you just found onto the file it applies to, so the next agent sees it in its first analysis call.
03
Checking a plan against the tests that already exist
Read the test intent strings the analysis returns and treat them as behavioural constraints instead of reading the whole test suite.
04
Looking up what the project already knows
Search the note store by topic or file path when you want the accumulated context without running a full analysis.
3 tools
Listed in project docs. Your client may show a different list.
save_project_noteread_project_notesBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @spectra-g/engram-adapterMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --scope user --transport stdio engram -- npx -y @spectra-g/engram-adapter
