Local History MCP
MCP ServerFree** – MCP server for accessing VS Code/Cursor's Local History.
Capabilities5 decomposed
vs code/cursor local history file retrieval
Medium confidenceExposes the local history storage mechanism used by VS Code and Cursor editors through an MCP server interface, enabling programmatic access to timestamped file snapshots stored in the editor's internal `.history` directory structure. The capability works by parsing the editor's local history metadata and file system layout to retrieve specific versions of files without requiring direct editor API access.
Bridges the gap between VS Code/Cursor's proprietary local history storage and external AI agents via MCP protocol, allowing LLMs to access editor history without plugin installation or direct API integration. Uses the editor's native file system layout rather than requiring editor-specific SDKs.
Unlike Git-based history (which requires commits) or manual backups, this provides automatic fine-grained snapshots at editor save intervals, accessible to AI agents through a standardized MCP interface without modifying the editor itself.
mcp protocol server implementation for editor integration
Medium confidenceImplements a Model Context Protocol (MCP) server that exposes local history as a standardized resource interface, allowing any MCP-compatible client (Claude Desktop, custom agents, LLM frameworks) to query and retrieve file history through a unified protocol. The server translates between the editor's internal history storage format and MCP's resource/tool abstraction layer.
Implements MCP as a first-class integration pattern for editor history, treating local history as a queryable resource rather than a file system artifact. Uses MCP's resource and tool abstractions to provide a clean, protocol-driven interface that works with any MCP-compatible client.
Compared to custom REST APIs or direct file system access, MCP provides a standardized, client-agnostic protocol that works with Claude Desktop and other MCP hosts without requiring custom client code or authentication infrastructure.
timestamped file snapshot querying
Medium confidenceEnables querying and retrieving specific file snapshots from the local history by timestamp, version number, or relative time references (e.g., 'last 5 minutes', 'before this commit'). The capability parses the editor's history metadata to locate and extract the exact file state at a given point in time, supporting both absolute and relative temporal queries.
Provides temporal query semantics over editor history snapshots, supporting both absolute timestamps and relative time expressions. Parses the editor's internal history metadata to map timestamps to file versions without requiring the editor to be running.
Unlike Git history (which requires explicit commits), this provides automatic snapshots at save intervals with precise timestamps, enabling fine-grained temporal queries without manual version control discipline.
multi-file history aggregation and listing
Medium confidenceAggregates and lists all files present in the local history, optionally filtered by file type, modification time, or directory path. The capability scans the editor's history storage structure and returns a consolidated view of which files have been edited, when they were last modified, and how many snapshots exist for each file.
Provides a unified view across the entire local history storage, aggregating metadata from multiple editor history entries into a queryable, filterable list. Enables project-wide history analysis without iterating through individual files.
Unlike Git log (which requires commits), this provides automatic aggregation of all edited files with fine-grained timestamps, and unlike manual file browsing, it scales to projects with hundreds of edited files.
editor-agnostic history format parsing
Medium confidenceParses and abstracts the internal storage format used by VS Code and Cursor to store local history, translating proprietary file system layouts and metadata formats into a normalized, editor-agnostic representation. The capability handles differences between VS Code and Cursor history storage while presenting a unified interface to clients.
Implements a format-agnostic parser that handles both VS Code and Cursor history storage layouts, normalizing their differences into a unified data model. Allows the MCP server to support multiple editors without duplicating logic.
Unlike editor-specific plugins (which require separate implementations per editor), this provides a single server that works with multiple editors by abstracting their storage formats at the parsing layer.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Local History MCP, ranked by overlap. Discovered automatically through the match graph.
codemirror-mcp
** CodeMirror extension that implements the Model Context Protocol (MCP) for resource mentions and prompt commands.
@iflow-mcp/cursor-mcp
[](https://smithery.ai/server/cursor-mcp-tool)
@theia/ai-mcp-server
Theia - MCP Server
oroute-mcp
O'Route MCP Server — use 13 AI models from Claude Code, Cursor, or any MCP tool
MCP Linker
** - A cross-platform Tauri GUI tool for one-click setup and management of MCP servers, supporting Claude Desktop, Cursor, Windsurf, VS Code, Cline, and Neovim.
CodeGraphContext
An MCP server plus a CLI tool that indexes local code into a graph database to provide context to AI assistants.
Best For
- ✓AI agents and LLM-based tools that need to reason about file evolution
- ✓Developers building custom IDE extensions or external tooling around VS Code/Cursor
- ✓Teams using MCP-compatible clients (Claude Desktop, custom agents) who want history context
- ✓Developers building MCP-compatible AI agents and LLM applications
- ✓Teams using Claude Desktop who want to give Claude access to local file history context
- ✓Organizations standardizing on MCP for tool integration across multiple development tools
- ✓Developers debugging issues by examining file state at specific moments
- ✓AI agents performing root-cause analysis by comparing historical file versions
Known Limitations
- ⚠Only accesses local history stored on the same machine — no remote history sync support
- ⚠Limited to VS Code and Cursor editors; other IDEs with different history storage formats are not supported
- ⚠History retention depends on editor settings; older snapshots may be automatically pruned
- ⚠No write capability — read-only access to historical snapshots
- ⚠MCP protocol overhead adds latency compared to direct file system access
- ⚠Server must be running separately from the editor — no built-in daemon management
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** – MCP server for accessing VS Code/Cursor's Local History.
Categories
Alternatives to Local History MCP
Are you the builder of Local History MCP?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →