Claude Server MCP
# Claude Server MCP
> **ARCHIVED** — This project is no longer maintained (March 2026).
## Why archived
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:
- **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
This project never progressed beyond v0.1.0 (6 commits, no tests, no production users).
## What it was
A Model Context Protocol (MCP) server providing:
- Hierarchical project context organization
- Session-based conversation tracking
- JSON-based persistent storage at `~/.claude/`
## Alternatives
- **Claude Code's built-in memory system** — does everything this project attempted, natively
- **CLAUDE.md files** — project-specific context that persists across sessions
- **MCP resources** — Claude Code's native MCP integration for external context
## License
MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_context retrieves a specific context, list_contexts lists contexts with filters, save_conversation_context saves conversation-specific context, and save_project_context saves project-specific context. The descriptions clearly differentiate between retrieval, listing, and two types of saving operations.
All tools follow a consistent verb_noun pattern (get_context, list_contexts, save_conversation_context, save_project_context) with clear, descriptive names. The naming convention is uniform throughout the set, making it easy to understand each tool's function at a glance.
With 4 tools, the count is reasonable for a context management server, covering key operations like retrieval, listing, and saving. It feels slightly minimal but well-scoped, as each tool serves a distinct and necessary function without redundancy.
The tool set provides good coverage for context management with get, list, and save operations for both conversation and project contexts. A minor gap exists in update or delete functionality for contexts, but agents can likely work around this by re-saving or managing contexts through the provided tools.