Engraphis

Your coding agent forgets decisions between sessions. Engraphis gives MCP-capable coding agents one local memory store with receipts.

Engraphis stores scoped project knowledge in SQLite, keeps temporal history instead of silently overwriting it, and returns bounded context with citations, or abstains when the evidence is weak. The local core is Apache-2.0 and works offline.

Watch the demo · Open the interactive demo · See how it compares

Star the repo so other coding-agent users can find it.

^{The Graph & Relations view at 127.0.0.1:8700. The full local dashboard is in the details below.}

Install and connect an agent in three commands

The MCP server and [all] extras need Python 3.10 or newer. The NumPy-only core still supports Python 3.9+.

python -m pip install "engraphis[mcp]"
engraphis-init
claude mcp add engraphis -- engraphis-mcp

engraphis-init writes a local config, generates an API token, and prints ready-to-paste setup for Claude Code, Codex, Cursor, Cline, Zed, and Windsurf. Use the exact command it prints for your machine, including the database path. Restart your agent, then ask it to remember a project decision and recall it in a new session.

If your client times out while the local embedding model loads, run engraphis-init --prefetch once.

For Cursor, Cline, Zed, or Windsurf, paste the JSON block printed by engraphis-init into the client's MCP configuration. Read the agent setup guide for the full setup.

Prefer the full local dashboard or the graph view?

python -m pip install "engraphis[all]"
engraphis-dashboard

The dashboard opens at http://127.0.0.1:8700. The [all] extra adds the embedding model, document import, and transcription dependencies. Most coding-agent users only need [mcp]. Local use needs no cloud account or API key.

^{Explore memories and their relationships in the local dashboard.}

Use the Python service directly

from engraphis.service import MemoryService

memory = MemoryService.create("engraphis.db")
memory.remember("Auth migrated from JWT to PASETO.", workspace="acme", repo="api")
hit = memory.recall("Why did we change auth?", workspace="acme", repo="api")
print(hit["context"])

What it provides

• Continuity: Organize memories by workspace, repository, and session, with a last-session handoff.
• Useful recall: Combine vector, lexical, graph, and code-aware retrieval, then pack results to a hard context budget.
• Grounded answers: Preserve provenance and temporal history; cite support or abstain when it is insufficient.
• Temporal history: Timeline can select known versions whose validity has ended before result limits. The dashboard uses closed_only=true on GET /api/timeline for “Only superseded versions.” Closed history prioritizes lexical matches (the literal query and up to 32 expanded terms, using the final ranker's Unicode lowercasing) before scoring at most 500 eligible candidates; semantic-only matches outside that window can be omitted. SQLite may scan and sort more rows than this candidate cap.
• Spec Studio: Inspect prompt specifications and scoped memory clusters with deterministic coverage, ambiguity, and conflict checks; review suggestions before changing memory.
• Operator control: Keep the core local and offline-capable, with explicit controls for hosted services and external LLM providers.
• Free Jev on paid plans: Pro and Team include managed Jev decisions up to 500 calls per person per day, with no personal provider key.

Why upgrade to Pro or Team

The local core stays free and offline-capable. Pro and Team add hosted workflows for memory that has to follow you across agents, machines, and teammates:

• See memory health: Analytics surfaces growth, retention, and decay forecasts so you can review what is becoming stale before it affects recall.
• Keep memory maintained: Schedule Auto Consolidation and Auto Dreaming. They produce proposals for you to review, and local governance still decides what changes.
• Sync across machines: Opt into encrypted Cloud Sync for eligible workspaces with a key you hold. Sync and readable managed processing are separate choices.
• Give a team an operating picture: Named seats, admin/member/viewer roles, scoped credentials, and a 30-day account activity log visible to owners and admins. Shared hosted Team memory and hosted MCP are not yet available.
• Add judgment with Jev: Pro and Team include up to 500 managed Jev calls per person per day: typed, advisory checks for risky commands, contradictory memories, evidence support, and completion claims. No personal TypeSafe key or overage charge. Jev helps an agent separate safe from risky actions, contradictory from reinforcing memories, supported from unsupported answers, and complete from unfinished work, while permissions and tests stay in charge.

Pro is $10/month or $100/year for one owner. Team is $20/seat/month or $200/seat/year. Both start with an email-confirmed, no-card trial (7 active days for Pro, 14 active days for Team). Compare plans · Start a Pro trial · Start a Team trial.

Benchmarks

The current registered artifact contains three deterministic offline fixture runs. It separates context size, retrieval quality, and grounded decision checks; these small fixtures do not establish general task performance.

^{Three offline fixtures separate context reduction, candidate and packed retrieval quality, and grounded behavior. The chart shows the artifact checksum prefix; see the benchmark guide for the full checksum and reproduction steps.}

Fixture	Result	Quality check
Structure-aware chunking	Mean retrieved top-5 context: 740.3 → 214.3 tokens per question (71.1% lower, 18 questions)	Recall@5 = 1.000 in both modes
Recall payload proxy	JSON-shape proxy: 24,590 → 11,138 tokens (54.71% lower, 26 samples; 260 timed recalls)	Candidate and packed Recall@5, Hit@5, and answer-token recall are each 1.000
Grounded decisions	5/5 answerable queries grounded; 6/6 abstention queries rejected, including 1/1 quarantined-evidence check	11/11 decisions correct

The payload figure is a serialized JSON-shape estimate, not an MCP transport measurement or provider billing total. See the Benchmark methodology for artifact identity, counting methods, reproduction commands, external-evaluation boundaries, and limitations.

Optional Jev assistance

Jev is included free with every paid plan: Pro and Team. Every legitimate Pro user and each eligible Team named seat, including paid viewers, with an active paid, trial, or test entitlement receives managed Jev at no additional customer charge and without a personal provider key. Local advisory decisions stay free for everyone; BYOK, a personal TypeSafe key, is optional for non-paid or direct use and its provider charges may apply. Managed Jev is available for paid plans; the hosted control service enables it with its provider key.

Each paid individual receives up to 500 Jev calls per person per day, free. Usage is per person, not pooled across a Team and not monthly. Each evaluated call counts once, including a batched request; calls beyond the daily maximum are not served. Admitted attempts that fail or are interrupted remain counted, and no overage is charged. The account portal reports that member's remaining calls for the current day.

Use Review with Jev in the local dashboard for evidence-support and contradiction checks; the MCP decision tool covers command and completion reviews. Remote calls need per-call consent plus a public or internal classification, and Jev cannot write memories, change grounded-recall requirements, authorize commands, or certify completion.

Recall route selection is experimental and BYOK-only: engraphis_recall_context with allow_remote=true, or classic MCP with planning="auto" and jev_assisted=true. On 40 public synthetic tasks it changed no retrieval quality, so no retrieval-quality improvement is claimed.

See hosted plans and Jev details.

Guides

• Configuration reference
• MCP tool reference
• Agent and LLM provider setup
• Architecture and query planning
• Docker deployment
• Document import
• Cloud Sync
• Pi extension
• Spec Crawl and Spec Studio
• Memory write review
• Coding-agent file protection
• Security policy
• Hosted plans and licensing

License

Engraphis is licensed under Apache-2.0. The license does not grant trademark rights. See LICENSE, NOTICE, and the licensing guide. The hosted control plane and managed services are private services.