Claude Server MCP
Related Servers
Alternatives to Claude Server MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides 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.122 npm135MIT

Threadminder MCPofficial
FlicenseNot gradedqualityFmaintenanceA persistent context layer for Claude that automatically remembers project status, decisions, and next actions across sessions, eliminating the need to re-explain context.-- AlicenseAqualityAmaintenanceProvides persistent, cross-project memory for Claude over the Model Context Protocol, enabling it to remember goals, decisions, and progress between sessions with deterministic briefs and supersession-aware recall.72MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for Claude Desktop that provides structured memory management across chat sessions, allowing Claude to maintain context and build a knowledge base within project directories.6 npm6MIT
- AlicenseNot gradedqualityDmaintenanceProvides Claude with a persistent local memory and structured knowledge graph to track project states, tasks, and historical decisions across different chat sessions. It enables users to recall information using keyword relevance, time-travel queries, and dependency analysis for complex project management.MIT
- FlicenseAqualityDmaintenanceProvides persistent personal context storage across AI conversations, allowing AI assistants to remember user preferences, project conventions, and other personal information between sessions.8-
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.