Skip to main content
Glama
Leviathan0x0

Chronicle MCP

by Leviathan0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Chronicle MCP

No user-submitted related servers found.

    Related Servers

    • Quaid

      SEEDO-Media-Ltd
      A
      license
      Not graded
      quality
      D
      maintenance
      Capture, index, and search your Claude Code conversation history. Provides an MCP server for Claude Code to query its own past conversations.
      1 npm
      1
      MIT

    • cc-channel-mem

      AlexAI-MCP
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server and background daemon that captures Discord and Telegram conversations locally to provide persistent memory for Claude Code sessions. It enables hybrid search and automatic context injection of chat history to maintain continuity across development sessions.
      1 npm
      22
      MIT

    • memex

      dioniipereyraa
      A
      license
      A
      quality
      D
      maintenance
      MCP server that indexes Claude.ai chats and local Claude Code sessions, enabling semantic and keyword search across all your conversations with Claude.
      6
      34 PyPI
      5
      MIT

    • Memex

      arnavbee
      A
      license
      A
      quality
      B
      maintenance
      A local-first, privacy-first MCP server that passively indexes personal digital activity (screenshots, clipboard, notes, downloads, links) into a local database, enabling LLMs like Claude to access your context without cloud storage.
      4
      1
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a distinct role, and the descriptions actively cross-reference each other (search_history vs get_chat_logs, sync_workspace_data vs manage_session_state). Minor overlap remains between manage_session_state's export/save actions and compile_project_insights' project_brief export, and between sync_workspace_data's import and manage_session_state's save, but the descriptions steer agents correctly.

    Naming Consistency5/5

    All eight tools use consistent snake_case verb_noun naming (search_history, get_chat_logs, save_handoff_receipt, get_handoff_status, etc.). The two handoff tools form a clean save/get pair, and no camelCase or vague verbs appear.

    Tool Count5/5

    Eight tools is well-scoped for an archive memory server: search, read, import, digest, housekeeping, session persistence, and a two-tool handoff lifecycle. Each tool covers a meaningful capability with no filler.

    Completeness4/5

    Chat lifecycle is well covered: create/import (sync_workspace_data), read (get_chat_logs), update (merge), delete, export, plus compression, dedupe, settings, and handoff open/close with staleness. Minor gaps: no direct tool to read a handoff receipt's full body (must go through search/get_chat_logs) and no way to update chat metadata or titles.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources