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
Exposes file snapshots captured at save points through MCP tools including history listing, content search, and restoration with automatic backups—bridging the gap between AI assistants and editor local history data. Implements stdio transport compatible with Cursor, Claude, and VS Code integrations, enabling AI-powered recovery and context awareness beyond traditional undo/redo functionality.
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.
Implements a Model Context Protocol (MCP) server with Turso database backend, organizing memory into four complementary systems: short-term (recent messages/files), long-term (milestones/decisions), episodic (chronological events), and semantic (vector embeddings for code/content similarity). The architecture auto-indexes code structures across languages, performs approximate nearest-neighbor search for fast retrieval, and provides unified context retrieval ranked by relevance—enabling Claude in Cursor to maintain deep project understanding across development sessions without external documentation overhead.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work