Local History
This MCP server provides direct access to Cursor/VS Code Local History data for AI-powered data recovery and enhanced context awareness, built by xxczaki using TypeScript with the MCP SDK and pino logging. The implementation bridges the gap between AI assistants and editor Local History by parsing history directories across platforms (Windows, macOS, Linux), offering six specialized tools for listing files with history, retrieving complete file histories, accessing specific history entries, restoring files to previous states with backup creation, searching across all history content, and generating statistics. Designed for developers who need programmatic access to their editor's Local History for data recovery scenarios, code analysis, and situations where current AI assistants cannot access this valuable historical context that captures file snapshots at save points.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-01.
Scan details: Circle-IR · 2026-09-01 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- monitoring
- Source
- PulseMCP
- Repository
- github.com/xxczaki/local-history-mcp
- Author type
- human
- Last scanned
- 2026-09-01
- Updated
- 2026-09-01
Use via MCP
Resolve Local History from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp --scope user for --scope project to commit it to .mcp.json.