Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Ranked local code-graph context for AI coding agents. Intercepts reads + greps. Apache-2.0.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ENGRAM_API_TOKEN, ENGRAM_MISTAKE_GUARD, ENGRAM_ANTHROPIC_MEMORY_PATH, ENGRAM_MCP_CONFIG_PATH, ENGRAM_NO_UPDATE_CHECKValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"engram": {
"command": "npx",
"args": [
"-y",
"engramx"
],
"env": {
"ENGRAM_API_TOKEN": "your-value",
"ENGRAM_MISTAKE_GUARD": "your-value",
"ENGRAM_ANTHROPIC_MEMORY_PATH": "your-value",
"ENGRAM_MCP_CONFIG_PATH": "your-value",
"ENGRAM_NO_UPDATE_CHECK": "your-value"
}
}
}
}Run this in your terminal
claude mcp add engram --env ENGRAM_API_TOKEN=your-value --env ENGRAM_MISTAKE_GUARD=your-value --env ENGRAM_ANTHROPIC_MEMORY_PATH=your-value --env ENGRAM_MCP_CONFIG_PATH=your-value --env ENGRAM_NO_UPDATE_CHECK=your-value -- npx -y engramxFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"engram": {
"command": "npx",
"args": [
"-y",
"engramx"
],
"env": {
"ENGRAM_API_TOKEN": "your-value",
"ENGRAM_MISTAKE_GUARD": "your-value",
"ENGRAM_ANTHROPIC_MEMORY_PATH": "your-value",
"ENGRAM_MCP_CONFIG_PATH": "your-value",
"ENGRAM_NO_UPDATE_CHECK": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"engram": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"engramx"
],
"env": {
"ENGRAM_API_TOKEN": "your-value",
"ENGRAM_MISTAKE_GUARD": "your-value",
"ENGRAM_ANTHROPIC_MEMORY_PATH": "your-value",
"ENGRAM_MCP_CONFIG_PATH": "your-value",
"ENGRAM_NO_UPDATE_CHECK": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
ENGRAM_MISTAKE_GUARD envENGRAM_ANTHROPIC_MEMORY_PATH envENGRAM_MCP_CONFIG_PATH envENGRAM_NO_UPDATE_CHECK envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account NickCirv, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ENGRAM_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (4.5.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server for Georgian public data, read from the organizations that publish it.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A local structural code graph and context toolkit for AI coding agents. Engram indexes source entities, Git relationships and selected project memory, then exposes focused context through a CLI, agent hooks, MCP and an authenticated local dashboard.
Use it to find relevant code before reading full files, inspect relationships and carry recorded mistakes into a later session. Read the source returned by a query before making a behavioral claim: graph retrieval is an aid to investigation.
The inspected package is engramx 4.5.0 and requires Node >=20. This source-build example is source-inspected, not executed; it does not assume a currently published package or extension version.
git clone https://github.com/NickCirv/engram.git
cd engram git checkout 9fa2a4b74ca8e66560d74d1255c16c43157d32bd npm install --ignore-scripts npm run build export ENGRAM_NO_UPDATE_CHECK=1 node dist/cli.js init ../your-project --no-hook node dist/cli.js query "authentication" --project ../your-project --budget 2000 node dist/cli.js stats --project ../your-project
Replace ../your-project with a codebase you can inspect. Indexing writes the project's .engram/ graph. The --no-hook flag matters: the default CLI init also installs a Sentinel hook. Start with the graph, examine the output, then decide which integration to enable. The build includes grammar bundling; inspect package scripts and dependencies before installation.
The query returns matching graph entities and an estimated token count, or a no-matching-nodes message. Counts depend on the indexed project; no benchmark output is fabricated here.
| Workflow | Source-backed entry points |
|---|---|
| Explore structure | query, path, gods, callers, callees, impact, stats |
| Maintain context | init, watch, reindex, learn, mistakes |
| Generate agent documents | gen, gen-mdc, gen-aider, gen-windsurfrules, gen-ccs |
| Inspect hook integration | install-hook --dry-run, hook-preview, hook-stats, hook-disable, hook-enable |
| Serve context | server, ui, engram-serve MCP executable |
| Review measurements | measure, bench, cost, package benchmark scripts |
| Maintain installation | doctor, setup --dry-run, update --check, database/cache/plugin commands |
These entry points are declared in the pinned CLI. Consult each command's help before a write operation. Generators, hook installers, cache/database commands and plugin installation can modify local state.
Source miners extract entities, references, Git co-change and selected mistake/session information. The graph store persists project-local SQLite using sql.js. Queries traverse the graph and render bounded context. The provider resolver combines built-in sources and optional plugins/MCP providers; integrations can add external processes and network access.
The architecture and integration guide maps these paths, documents HTTP authentication and gives a local MCP configuration. Existing design records, release notes, integration documents and the ECP draft remain linked in the documentation inventory. They retain historical context and are not all certified against this revision.
The core graph is local, but the entire system is not guaranteed to be network-free. The CLI has npm update checks, Context7 can call an external wrapper, and configured MCP/plugin providers can execute their own processes. ENGRAM_NO_UPDATE_CHECK=1 disables the update-check path; it does not disable every optional integration. Review configured providers and the agent that receives graph output.
The HTTP server binds to 127.0.0.1, validates Host/Origin and requires a bearer token or dashboard cookie for protected routes. It resolves a token from ENGRAM_API_TOKEN or a local token file. Keep that token private and retain the existing security policy.
Structural context size, estimated token reductions, session replay and actual provider billing answer different questions. A smaller packet does not by itself demonstrate equal answer quality or a lower bill. Reproduce the included benchmarks on your own representative workload and track correctness alongside cost. This documentation review did not run a build, test suite, benchmark or agent session.
npm run build
npm run lint npm test -- --run
The repository contains unit and integration test sources for graph storage, providers, hooks, HTTP security and other modules. Their presence is evidence of test coverage intent; results at this revision remain unverified here. See the preserved contribution guide before changing behavior.
Apache-2.0 license. The ECP specification carries its own attribution and licensing in its source document; this rewrite does not alter either.
Nicholas Ashkar · Applied AI, systems and consulting.
User manual covers setup, skills, troubleshooting and removal. Sentinel explains current hook behavior and guard modes. Tool authors can use the integration guide.