Claude Server MCP
The Claude Server MCP provides sophisticated context management for Claude, enabling persistent, organized, and efficient storage of project and conversation contexts.
Save Project Contexts: Store project-specific contexts with hierarchical organization, parent-child relationships, and metadata
Save Conversation Contexts: Maintain conversation continuity across sessions with tagging and chaining
Retrieve Contexts: Fetch specific contexts by ID for quick access
List Contexts: Filter contexts by tags, type, or project ID for better organization
Efficient Storage: Uses structured directory (~/.claude/) and JSON-based storage for quick lookups
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Claude Server MCP save this conversation about the new API design to project 'mobile-app'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 conversationsCLAUDE.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).
Related MCP server: Threadminder MCP
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
Available Tools
4 toolsget_contextC
Retrieve context by ID and optional project ID
Inputs: id (required), projectId.
list_contextsC
List contexts with filtering options
Inputs: projectId, tag, type.
save_conversation_contextC
Save conversation context with continuation support
Inputs: id (required), sessionId (required), content (required), continuationOf, +2 more.
save_project_contextC
Save project-specific context with relationships
Inputs: id (required), projectId (required), content (required), parentContextId, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
Share one project context across ChatGPT, Claude, Telegram and any MCP client.
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
Cross-LLM persistent memory: store context once, recall it from any AI model.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides persistent context management for Claude AI coding assistants, allowing you to save and restore conversation context, create checkpoints, and organize information across sessions to prevent losing important work history and decisions during long coding sessions.243 npm136MIT

Threadminder MCPofficial
FlicenseNot gradedqualityDmaintenanceA persistent context layer for Claude that automatically remembers project status, decisions, and next actions across sessions, eliminating the need to re-explain context.-- AlicenseNot gradedqualityBmaintenanceEnables persistent context management for Claude AI coding assistants by saving, searching, checkpointing, restoring, and sharing project context across sessions and parallel conversations.243 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent context management for Claude AI coding assistants, enabling users to save, search, checkpoint, restore, and share project context across sessions and parallel sessions. It preserves work history, decisions, and progress so coding workflows survive compaction and context limits.243 npmMIT