{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-local-history-mcp","slug":"local-history-mcp","name":"Local History MCP","type":"mcp","url":"https://github.com/xxczaki/local-history-mcp","page_url":"https://unfragile.ai/local-history-mcp","categories":["mcp-servers","app-builders"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-local-history-mcp__cap_0","uri":"capability://tool.use.integration.vs.code.cursor.local.history.file.retrieval","name":"vs code/cursor local history file retrieval","description":"Exposes 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.","intents":["Access previous versions of a file without opening the editor's history UI","Retrieve a specific historical snapshot of a file by timestamp or version number","Integrate file history data into external tools or AI agents for analysis","Programmatically query what files have been edited and when in the local history"],"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"],"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"],"requires":["VS Code 1.70+ or Cursor (any recent version) with local history enabled","MCP client compatible with the server (Claude Desktop, custom MCP host, or agent framework)","File system access to the editor's local history directory (typically ~/.vscode/User/History or equivalent)"],"input_types":["file path (string)","timestamp or version identifier (optional)","query parameters for filtering history entries"],"output_types":["file content (text/code)","metadata (timestamps, file paths, version identifiers)","structured history listing (JSON)"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-local-history-mcp__cap_1","uri":"capability://tool.use.integration.mcp.protocol.server.implementation.for.editor.integration","name":"mcp protocol server implementation for editor integration","description":"Implements 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.","intents":["Enable Claude Desktop and other MCP clients to access file history without custom plugins","Provide a standardized interface for AI agents to query historical file versions","Integrate local history into LLM-powered development workflows via MCP tools","Allow external applications to subscribe to or poll file history changes through MCP"],"best_for":["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"],"limitations":["MCP protocol overhead adds latency compared to direct file system access","Server must be running separately from the editor — no built-in daemon management","No authentication/authorization layer — assumes trusted local network or single-user machine","Limited to MCP protocol capabilities; advanced editor features (diff visualization, merge) not exposed"],"requires":["MCP server runtime (Node.js 18+ or equivalent)","MCP client that supports resource and/or tool protocols","Network connectivity between client and server (localhost or LAN)"],"input_types":["MCP resource requests (file paths, version identifiers)","MCP tool invocations with parameters"],"output_types":["MCP resource responses (file content, metadata)","MCP tool results (structured data, file snapshots)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-local-history-mcp__cap_2","uri":"capability://search.retrieval.timestamped.file.snapshot.querying","name":"timestamped file snapshot querying","description":"Enables 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.","intents":["Retrieve the state of a file at a specific point in time during a debugging session","Compare file versions across multiple timestamps to understand how code evolved","Find the last working version of a file before a breaking change was introduced","Access file history for audit or compliance purposes with precise timestamps"],"best_for":["Developers debugging issues by examining file state at specific moments","AI agents performing root-cause analysis by comparing historical file versions","Teams needing audit trails of file changes with exact timestamps"],"limitations":["Timestamp precision depends on editor's history granularity (typically per-save, not per-keystroke)","Relative time queries require system clock accuracy and timezone awareness","No support for querying across multiple files' synchronized states at a single point in time","History data is local only — no cross-machine or cloud-based timestamp correlation"],"requires":["File must exist in local history with at least one snapshot","Timestamp must fall within the retention window of the editor's history settings","System clock must be reasonably accurate for relative time queries"],"input_types":["file path (string)","timestamp (ISO 8601 or Unix epoch)","relative time reference (string, e.g., '5 minutes ago')","version identifier (integer or hash)"],"output_types":["file content at specified timestamp (text/code)","metadata including exact timestamp and version info (JSON)","list of available snapshots within a time range (JSON array)"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-local-history-mcp__cap_3","uri":"capability://data.processing.analysis.multi.file.history.aggregation.and.listing","name":"multi-file history aggregation and listing","description":"Aggregates 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.","intents":["Get an overview of which files have been edited recently in the current project","Find all files modified within a specific time window for change tracking","Identify files with the most history snapshots (most actively edited files)","Filter history by file type (e.g., 'show me all .ts files edited in the last hour')"],"best_for":["AI agents performing project-wide analysis or change impact assessment","Developers reviewing what files were modified during a specific time period","Teams tracking code churn or identifying frequently-modified files"],"limitations":["Listing performance degrades with very large histories (thousands of files with many snapshots)","No recursive directory filtering — must query by explicit path patterns","Aggregation is point-in-time; no streaming or incremental updates","File type filtering is based on extension only; no content-based classification"],"requires":["Local history directory must be readable and contain valid history metadata","Sufficient memory to load and aggregate all history entries"],"input_types":["optional filter criteria (file type, time range, directory path)","optional sorting preference (by timestamp, by snapshot count, alphabetical)"],"output_types":["structured list of files with metadata (JSON array)","file metadata including last modified time, snapshot count, file size","summary statistics (total files, total snapshots, date range)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-local-history-mcp__cap_4","uri":"capability://data.processing.analysis.editor.agnostic.history.format.parsing","name":"editor-agnostic history format parsing","description":"Parses 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.","intents":["Support both VS Code and Cursor editors with a single MCP server implementation","Abstract away editor-specific history storage details from client code","Enable future support for additional editors by extending the parser","Normalize history metadata across different editor versions"],"best_for":["Tool developers building editor-agnostic history integrations","Teams using both VS Code and Cursor who want unified history access","Framework authors extending MCP server support to multiple editors"],"limitations":["Parser must be updated when editors change their history storage format","Differences in history retention policies between editors may cause inconsistent behavior","No support for editors other than VS Code and Cursor without code changes","Metadata normalization may lose editor-specific information (e.g., Cursor-specific fields)"],"requires":["Knowledge of VS Code and Cursor history storage formats","Access to the editor's configuration directory"],"input_types":["raw history file system paths and metadata from editor storage"],"output_types":["normalized history metadata (JSON)","abstracted file snapshot references"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"high","permissions":["VS Code 1.70+ or Cursor (any recent version) with local history enabled","MCP client compatible with the server (Claude Desktop, custom MCP host, or agent framework)","File system access to the editor's local history directory (typically ~/.vscode/User/History or equivalent)","MCP server runtime (Node.js 18+ or equivalent)","MCP client that supports resource and/or tool protocols","Network connectivity between client and server (localhost or LAN)","File must exist in local history with at least one snapshot","Timestamp must fall within the retention window of the editor's history settings","System clock must be reasonably accurate for relative time queries","Local history directory must be readable and contain valid history metadata"],"failure_modes":["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","No authentication/authorization layer — assumes trusted local network or single-user machine","Limited to MCP protocol capabilities; advanced editor features (diff visualization, merge) not exposed","Timestamp precision depends on editor's history granularity (typically per-save, not per-keystroke)","Relative time queries require system clock accuracy and timezone awareness","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:20.442Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=local-history-mcp","compare_url":"https://unfragile.ai/compare?artifact=local-history-mcp"}},"signature":"LEY5n9RjYhuSXfHE5sVxqj93t3YpvFodkgcqHEIA/FVJkfWG5FWtxK/QHrp/SqEkMeY6o1v5PhqaNZS8TSQEAg==","signedAt":"2026-06-17T04:49:57.517Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/local-history-mcp","artifact":"https://unfragile.ai/local-history-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=local-history-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}