Skip to main content
Glama
dambinhtu-nhuy

claude-code-session-mcp

by dambinhtu-nhuy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to claude-code-session-mcp

No user-submitted related servers found.

    Related Servers

    • claude-replay

      constripacity
      A
      license
      A
      quality
      A
      maintenance
      Enables search, analytics, and visualization of Claude Code sessions with MCP tools for session management, recovery, and insights.
      10
      1
      MIT

    • agentops-mcp

      Ludoonus
      A
      license
      A
      quality
      C
      maintenance
      Exposes analytics from Claude Code transcripts as MCP tools, enabling cost, audit, safety, and efficiency queries through natural language.
      4
      MIT

    • Claude Code History MCP Server

      yudppp
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables users to retrieve, filter, and search through Claude Code conversation history stored in local projects. It provides tools for listing projects and sessions, paginating through message history, and searching across conversations with keyword filtering.
      4
      8 npm
      11
      MIT

    • transcript-search-v2

      jsundquist
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that indexes local Claude Code transcripts and provides keyword, phrase, semantic, and date-range search, plus full context/session recall.
      -
    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 distinctly separate purpose: list_sessions provides an overview for browsing, session_stats drills into a single session's aggregate counts, and tool_usage analyzes tool call frequencies across sessions. There is no overlap or ambiguity in what each tool returns.

    Naming Consistency4/5

    list_sessions follows a verb-noun pattern, while session_stats and tool_usage are noun-noun, but all use consistent snake_case and are immediately readable. The slight variation is predictable and does not cause confusion.

    Tool Count5/5

    With only three tools, the server is tightly scoped to session statistics and aggregation. This count is well within the ideal 3-15 range, and each tool serves a necessary, non-redundant function for the stated purpose.

    Completeness5/5

    The tool set fully covers the intended workflow: listing sessions, viewing detailed stats for a specific session, and aggregating tool usage across sessions. The deliberate omission of message content is consistent with the server's focus on counts, leaving no obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources