Project memory for Claude: decisions, pipelines, and constraints across conversations.
Most knowledge and memory work still happens through a UI a human drives. Context MCP server moves it into the conversation instead. Project memory for Claude: decisions, pipelines, and constraints across conversations.
Project memory for Claude. Records design decisions, pipeline flows, and constraints so Claude maintains context across conversations.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
The server publishes 14 tools. What each one is for:
Abstention — measures whether get_context says "nothing relevant" instead of confabulating on no-answer queries; the 0.20 relevance floor is the highest with zeroOver — budget summaries are now floored and reported.** Truncating therecord_entry — Unified write tool — record a decision, pipeline, or constraint via kind, with per-kind fields validated server-side. Consolidates the formerget_context — Retrieve relevant entries by query, tags, scope, or ID — relevance-ranked, pulls related_to links by defaultquery_entries — Exact structured-field filtering (status, origin, tags, scope, hardness, supersession, dates) — deterministic, no ranking; distinct fromget_project_summary — Compact overview for conversation startupdate_entry — Update any entry by IDdeprecate_entry — Retire an entry with reason (optional merge_into folds a duplicate into a survivor)prune_stale — Find entries not verified recentlyget_compaction_report — Check if last compaction lost any contextverify_quality — Scan entries for thin rationale, missing tags, isolated arcs (auto-called by PreCompact hook)export_markdown — Regenerate DECISIONS.md from the decisions store — a derived, read-only projectionAmong the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Context's toolset — Abstention, Over, record_entry and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jarmstrong158; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Context's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Abstention | measures whether get_context says "nothing relevant" instead of confabulating on no-answer queries; the 0.20 relevance floor is the highest with zero false-abstention on the eval set ([evals/abstention.py](evals/abstenti |
| Over | budget summaries are now floored and reported.** Truncating the |
| record_entry | Unified write tool — record a decision, pipeline, or constraint via kind, with per-kind fields validated server-side. Consolidates the former record_decision/record_pipeline/record_constraint (still dispatchable by those |
| get_context | Retrieve relevant entries by query, tags, scope, or ID — relevance-ranked, pulls related_to links by default |
| query_entries | **Exact structured-field filtering** (status, origin, tags, scope, hardness, supersession, dates) — deterministic, no ranking; distinct from get_context's relevance search |
| get_project_summary | Compact overview for conversation start |
| update_entry | Update any entry by ID |
| deprecate_entry | Retire an entry with reason (optional merge_into folds a duplicate into a survivor) |
| prune_stale | Find entries not verified recently |
| get_compaction_report | Check if last compaction lost any context |
| verify_quality | Scan entries for thin rationale, missing tags, isolated arcs (auto-called by PreCompact hook) |
| export_markdown | Regenerate DECISIONS.md from the decisions store — a derived, read-only projection |
| reload_constraints | Re-surface the constraints-only block on demand mid-session (rules refresh, not the full store) |
| export_snapshot | Write the whole store to a committable .context-keeper/memory.json.gz for sharing project memory via git |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.