Skip to main content
Glama
daniellmorris

local-claude-chat-history-mcp

by daniellmorris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to local-claude-chat-history-mcp

No user-submitted related servers found.

    Related Servers

    • context-bridge

      zachvp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to search and retrieve past chat history from Claude.ai exports and Claude Code sessions, allowing the AI to reference previous conversations and decisions.
      MIT

    • AI Memory MCP

      optimaquantum
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to semantically search your entire local conversation history from Claude Desktop, ChatGPT and Claude Code, and to retrieve, browse, ingest and report on those conversations. All embeddings run locally, so no cloud, API keys, or data leave your machine.
      1
      MIT

    • ccfolio

      Hippensteel
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and browsing past Claude Code conversations directly from within an active Claude session, with full-text search and cost tracking.
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_sessions for overview, search_history for finding specific content, and get_session for reading a full conversation. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_session, list_sessions, search_history) with snake_case, making the tool surface predictable.

    Tool Count5/5

    With 3 tools, the server is tightly scoped to its purpose—listing, searching, and reading chat history. No waste or missing core functionality.

    Completeness5/5

    The tool set covers the full lifecycle for a read-only history server: list to browse, search to find, and get to retrieve full content. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources