MCP server for persistent context management in AI coding assistants
If you already use MCP Memory Keeper, the mcp memory keeper mcp server is the piece that lets your assistant work with it directly. MCP server for persistent context management in AI coding assistants.
A Model Context Protocol (MCP) server that provides persistent context management for Claude AI coding assistants. Never lose context during compaction again! This MCP server helps Claude Code maintain context across sessions, preserving your work history, decisions, and progress.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Profile — Toolsminimal — 8standard — 22full — 38TOOL_PROFILE — Config file has profile?Set — YesVariable — DescriptionTOOL_PROFILE_CONFIG — Override config file path (default: ~/.mcp-memory-keeper/config.json)Troubleshooting — The Troubleshooting tool exposed by this servermcp-memory-keeper on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: TOOL_PROFILE, MCP_MAX_TOKENS, MCP_TOKEN_SAFETY_BUFFER, MCP_MAX_ITEMS, MCP_CHARS_PER_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Memory Keeper's toolset — Profile, minimal, standard and 6 more — is a fair guide to whether it matches your workflow. It is maintained by mkreyman; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Profile | Tools |
| minimal | 8 |
| standard | 22 |
| full | 38 |
| TOOL_PROFILE | Config file has profile? |
| Set | Yes |
| Variable | Description |
| TOOL_PROFILE_CONFIG | Override config file path (default: ~/.mcp-memory-keeper/config.json) |
| Troubleshooting | The Troubleshooting tool exposed by this server. |
{
"mcpServers": {
"memory-keeper": {
"command": "npx",
"args": ["mcp-memory-keeper"],
"env": {
"TOOL_PROFILE": "minimal"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TOOL_PROFILE | Configuration value read at startup. | Optional |
| MCP_MAX_TOKENS | Credential the server authenticates with. | Yes |
| MCP_TOKEN_SAFETY_BUFFER | Credential the server authenticates with. | Yes |
| MCP_MAX_ITEMS | Configuration value read at startup. | Optional |
| MCP_CHARS_PER_TOKEN | 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.