Skip to main content
Glama
ReclaimLLM

ReclaimLLM

Official
by ReclaimLLM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ReclaimLLM

No user-submitted related servers found.

    Related Servers

    • agent-bus

      rishabhjava
      A
      license
      A
      quality
      B
      maintenance
      Enables multiple coding agents (Claude Code, Codex, Cursor) to discover each other's sessions, search transcripts, ask questions, and handoff tasks through a shared MCP server.
      5
      2 npm
      MIT

    • Brain

      sdrshn-nmbr
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP server for collecting, searching, and sharing agent session history from Claude Code, Codex, and Cursor, with repository scoping and token-based authentication.
      Apache 2.0

    • 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.
      -

    • vibe-hnindex

      AndyAnh174
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server to index your codebase once and search it across AI sessions with keyword, semantic, or hybrid search, keeping all data on disk.
      85 npm
      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

    A4/5.0

    Scored across 14 tools

    Disambiguation3/5

    Most tools are clearly distinct (list_projects, get_session, summarize_session, handoff, transfer_session), but the replay family (replay_eligibility, replay_session, replay_corpus, replay_compare) and the search family (search_sessions, search_by_filename, filter_sessions) have overlapping boundaries that require careful reading. The descriptions do a good job of disambiguating, but an agent could still confuse replay_eligibility with replay_session, or search_sessions with filter_sessions.

    Naming Consistency4/5

    The naming is mostly consistent with verb_noun patterns (list_projects, search_sessions, filter_sessions, get_session, summarize_session, transfer_session, replay_eligibility, replay_session, replay_corpus, replay_compare). Minor deviations include file_brief and handoff, which use noun/verb-only forms instead of a clear verb_noun pattern, and search_by_filename breaks the pattern slightly.

    Tool Count5/5

    14 tools is a reasonable, well-scoped count for a session-management and replay-analysis server. Each tool serves a distinct purpose within the domain: discovery, retrieval, summarization, handoff, transfer, signals, and replay analysis. No tool feels redundant or superfluous.

    Completeness4/5

    The tool surface covers the core session lifecycle well: list/search/filter sessions, get/summarize sessions, file-based history, handoff, transfer, signals, and replay analysis. Minor gaps include no tool for deleting sessions or managing projects, but those are likely outside the server's stated purpose. The replay workflow is well covered with eligibility check, single-session replay, corpus replay, and comparison.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources