cursor-history-mcp and cursor10x-mcp

These are complements: the history tool provides raw chat history browsing and export, while the memory system builds persistent structured context and relationships on top of that data to enhance AI assistance across sessions.

cursor-history-mcp
42
Emerging
cursor10x-mcp
37
Emerging
Maintenance 13/25
Adoption 7/25
Maturity 18/25
Community 4/25
Maintenance 2/25
Adoption 9/25
Maturity 9/25
Community 17/25
Stars: 28
Forks: 1
Downloads:
Commits (30d): 0
Language: TypeScript
License: MIT
Stars: 77
Forks: 14
Downloads:
Commits (30d): 0
Language: JavaScript
License: MIT
No risk flags
Stale 6m No Package No Dependents

About cursor-history-mcp

S2thend/cursor-history-mcp

MCP server for browsing, searching, and exporting Cursor AI chat history.

Implements direct SQLite querying of Cursor's native database with grep-style text search instead of vector embeddings, enabling instant offline results without external LLM dependencies. Provides additional capabilities beyond browsing—including backup/restore, cross-workspace migration, and year-in-review analytics—all via an npx-based MCP server that integrates with Cursor IDE, Claude Desktop, and Claude Code with zero configuration.

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.

Scores updated daily from GitHub, PyPI, and npm data. How scores work