local-history-mcp and cursor10x-mcp
These are complementary tools: local-history-mcp provides access to VS Code/Cursor's built-in file version history, while cursor10x-mcp builds a separate persistent memory system for conversation context and code relationships, allowing them to work together to preserve both low-level code changes and high-level semantic understanding across sessions.
About local-history-mcp
xxczaki/local-history-mcp
MCP server for accessing VS Code/Cursor's Local History
This tool helps developers recover lost code or review past changes in their VS Code or Cursor editor. It takes your editor's Local History snapshots as input and allows AI assistants to understand and retrieve specific versions of your files. Developers, especially those working with AI coding tools, would use this to ensure no work is truly lost and to provide more context to their AI assistant.
About cursor10x-mcp
aiurda/cursor10x-mcp
The Cursor10x MCP is a persistent multi-dimensional memory system for Cursor that enhances AI assistants with conversation context, project history, and code relationships across sessions.
DevContext significantly enhances how AI assistants, like Claude, understand your coding projects. It acts like a persistent brain for your AI, remembering conversation history, active files, project decisions, and even the intricate relationships within your code. This means your AI assistant can provide much smarter, context-aware help, picking up right where you left off. Developers are the primary users, benefiting from a more seamless and intelligent AI-powered coding experience.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work