Skip to main content
Glama
xxczaki

Local History MCP Server

by xxczaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Local History MCP Server

No user-submitted related servers found.

    Related Servers

    • Cursor DB MCP Server

      TaylorChen
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying, searching, and analyzing Cursor IDE conversation history from SQLite workspaceStorage databases. Supports exporting chat data in multiple formats and provides workspace utilities for managing conversation data across projects.
      MIT

    • Coding Tools MCP

      R-HUA
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to develop within a local project workspace by reading and modifying files, running commands and tests, checking Git state, and persisting progress as history sessions that can be restored in later conversations.
      -

    • AITree MCP Server

      Paracci
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to generate annotated file trees, retrieve file statistics, list git-changed files, and read file contents from local directories or GitHub repositories.
      MIT

    • memgrep

      gitwork-oss
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and retrieve past chat transcripts from Cursor, Claude Code, and Kiro, providing a global, local memory for context-aware assistance.
      67 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation—retrieving full history, a specific entry, statistics, listing files, restoring, or searching—with no overlap in purpose.

    Naming Consistency5/5

    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.

    Tool Count5/5

    With six tools, the server covers core local history workflows without unnecessary complexity—appropriate for its focused scope.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources