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
      B
      maintenance
      Capture, index, and search your Claude Code conversation history. Provides an MCP server for Claude Code to query its own past conversations.
      6 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.
      4 npm
      22
      MIT

    • memex

      dioniipereyraa
      A
      license
      A
      quality
      B
      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
      6
      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
      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

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation: insights, logs, handoff status, storage maintenance, session management, handoff receipts, search, and data ingestion. No overlapping purposes, making selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., compile_project_insights, get_chat_logs). No mixing of styles, ensuring predictability.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its domain of workspace and chronicle management. Each tool serves a clear function without excess or insufficiency.

    Completeness5/5

    The tool set covers all key workflows: data ingestion, retrieval, search, analysis, maintenance, session management, and handoff procedures. No obvious gaps for the intended purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources