Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
Agent MCP server exists for a simple reason — assistants are far more useful when they can act on Agent directly instead of describing what you should do. Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
Claude Code memory that learns from corrections. The only learning loop that measures whether your agent actually stops repeating a mistake.
Once Agent is connected, these are the calls the assistant has available:
Metric — ValueLayer — TypePiece — What it doesPlatform — MechanismYou will need one environment variable: OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at agent-recall-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among 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. Agent's toolset — Metric, Layer, Piece and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Goldentrii; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Metric | Value |
| Layer | Type |
| Piece | What it does |
| Platform | Mechanism |
Generic MCP JSON for other clients:
```json
{ "mcpServers": { "agent-recall": { "command": "npx", "args": ["-y", "agent-recall-mcp"] } } }Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
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.