Memory Cache MCP Server
Related Servers
Alternatives to Memory Cache MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that optimizes token usage by caching data during language model interactions, compatible with any language model and MCP client.42-
- AlicenseAqualityCmaintenanceAn MCP server that helps AI agents reduce token usage by compressing, summarizing, and managing conversation/context data more efficiently.11MIT
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server providing pre-curated canonical memory, prose/code provenance checking, and benchmark metrics to improve accuracy and reduce costs across AI tools.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server for conversation compression that reduces token consumption using deterministic, embedding-free compression with mode-aware strategies.1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides persistent memory and conversation continuity for Claude Desktop and Claude Code, allowing users to save and restore project context when threads hit token limits.MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides knowledge graph-based persistent memory for LLMs, allowing them to store, retrieve, and reason about information across multiple conversations and sessions.9114,646 npm2MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: clear_cache removes entries, get_cache_stats provides metrics, retrieve_data fetches data, and store_data saves data. There is no overlap or ambiguity between these four operations.
The naming is mixed: clear_cache and get_cache_stats follow a verb_noun pattern, but retrieve_data and store_data use a verb_object pattern. While readable, this inconsistency in structure (cache vs. data as the object) deviates from a uniform convention.
With 4 tools, this is well-scoped for a memory cache server. It covers the essential operations (store, retrieve, clear, stats) without being overly sparse or bloated, making each tool necessary and focused.
The toolset covers core cache operations: storing, retrieving, clearing, and monitoring. A minor gap is the lack of an update or delete specific entry tool, but agents can work around this by using clear_cache for deletion and store_data for updates, so it's mostly complete.