Skip to main content
Glama
singleflo

opencode-history-mcp

by singleflo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to opencode-history-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      3 npm
      MIT

    • callimachus

      BetaBots-LLC
      A
      license
      A
      quality
      A
      maintenance
      Local index and hybrid search (SQLite FTS5 + on-device vector KNN) over your AI coding-agent conversation history across 11 tools (Claude Code, Codex, Cursor, and more). Exposes search_threads, search_current_project, recent_threads, get_thread, list_tags, and list_open_todos so any agent can recall its own past work.
      22
      39
      AGPL 3.0

    • MCP Memory

      PascalNoisette
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Kilo Code and Opencode conversation history stored in a local SQLite database, allowing users to list projects and sessions, read messages, and perform full-text keyword searches across all messages.
      -

    • Conversation Search MCP Server

      cordlesssteve
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables comprehensive search and analysis of Claude Code conversation history using full-text search, optional semantic vector search, and conversation management tools. Provides fast SQLite-based indexing with role-based filtering, project organization, and hybrid search capabilities combining keyword and semantic matching.
      -
    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.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    While search_history and find_related_work both search text, they target different fields (full conversation vs. titles/initial prompts) and the descriptions explicitly distinguish them. All other tools are clearly distinct by resource type (sessions, files, stats).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, with modifiers like 'by_file' and 'by_related_work' for clarity.

    Tool Count5/5

    Seven tools provide a tight, focused set for browsing session history without redundancy.

    Completeness5/5

    The tool set covers discovery (search, file lookup, related work, list), detail retrieval, message reading, and aggregate stats—no obvious dead ends for a read-only history server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources