This project aimed to provide persistent context management across Claude sessions via an MCP server. Since then, Claude Code has shipped native
This project aimed to provide persistent context management across Claude sessions via an MCP server. Since then, Claude Code has shipped native solutions that supersede this:. That is what the claude server mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 4 tools. What each one is for:
Auto — memory** (~/.claude/projects/*/memory/) — persistent, file-based memory across conversationsCLAUDE.md — project-level instructions loaded automatically into every sessionBuilt — in conversation continuity** — Claude Code now maintains context nativelySession — based conversation trackingSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
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. Claude Server's toolset — Auto, CLAUDE.md, Built and 1 more — is a fair guide to whether it matches your workflow. It is maintained by davidteren; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Claude Server's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Auto | memory** (~/.claude/projects/*/memory/) — persistent, file-based memory across conversations |
| CLAUDE.md | project-level instructions loaded automatically into every session |
| Built | in conversation continuity** — Claude Code now maintains context natively |
| Session | based conversation tracking |
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.