Skip to main content
Glama
Stefan-Nitu

MCP Claude Code Conversation History

by Stefan-Nitu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Claude Code Conversation History

No user-submitted related servers found.

    Related Servers

    • claude-kb

      tenequm
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and retrieving Claude Code conversation history via hybrid semantic and keyword search, allowing the agent to access its own past interactions.
      4
      MIT

    • 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

    • ccfolio

      Hippensteel
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching and browsing past Claude Code conversations directly from within an active Claude session, with full-text search and cost tracking.
      MIT

    • claude-lens

      sanchez314c
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to search and retrieve information from its past session transcripts, including tool calls, errors, and project-specific history, via an SQLite FTS5 full-text search index.
      2 npm
      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.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusing it with another tool. The tool's single purpose is clearly defined as searching across all Claude Code conversations.

    Naming Consistency5/5

    With only one tool, there is no inconsistent naming convention. The name 'claude_code_conversation_history' is descriptive and follows a clear pattern, making it easy for an agent to understand its purpose.

    Tool Count4/5

    The tool count of one is slightly below the typical range, but this single tool is well-designed with multiple internal actions (stats, list, search, read) that cover the full scope of conversation history access, so it does not feel thin or under-provisioned.

    Completeness5/5

    The tool provides comprehensive coverage for its domain: stats for overview, list for browsing, search for finding specific content, and read for detailed retrieval. This covers the essential lifecycle of conversation history access without obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources