Local History MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_history_filesA | List all files that have local history entries in VS Code |
| get_file_historyB | Get the complete history for a specific file |
| get_history_entryA | Get a specific history entry for a file |
| restore_from_historyB | Restore a file to a specific point in its local history |
| get_history_statsA | Get statistics about the local history (total files, entries, etc.) |
| search_history_contentB | Search for specific content across all history entries |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation—retrieving full history, a specific entry, statistics, listing files, restoring, or searching—with no overlap in purpose.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_file_history, restore_from_history), making the set predictable and easy to navigate.
With six tools, the server covers core local history workflows without unnecessary complexity—appropriate for its focused scope.
The tools provide a complete lifecycle: querying history, listing tracked files, retrieving entries, restoring files, and searching content—no obvious gaps for the stated purpose.