Skip to main content
Glama
gzmagyari

RepoChatMCP

by gzmagyari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to RepoChatMCP

No user-submitted related servers found.

    Related Servers

    • 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

    • engram-mcp

      lowbridgee
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables semantic and keyword search over Claude Code conversation history stored locally, using hybrid search, local embeddings, and time-decay scoring.
      10 npm
      MIT

    • flightlog

      RobHudson72
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that indexes Claude Code conversation history into SQLite, enabling full-text search across past sessions for context recovery and cross-agent observability.
      10
      3
      MIT

    • recall

      Zavelinski
      A
      license
      A
      quality
      C
      maintenance
      A zero-dependency MCP server for cross-session memory recall in Claude Code. Provides lexical search, listing, and retrieval of past session memories to avoid re-explaining context.
      3
      6 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

    A3.5/5.0

    Scored across 15 tools

    Disambiguation4/5

    Tools are mostly distinct, clearly separated into session management, chat search, and knowledge indexing. Some overlap exists between chat.search (relevance scoring) and chat.grep (regex), and among the various knowledge reading tools, but descriptions clarify their different purposes.

    Naming Consistency4/5

    All tools use snake_case and the chat. prefix, generally following a verb_noun pattern (list_sessions, read_session, start_knowledge_index). There is one deviation ('compaction_knowledge' is noun-like) and a mix of verbs like search/grep/read, but overall the naming is consistent and readable.

    Tool Count5/5

    15 tools is within the ideal 3-15 range for a focused MCP server. Each tool addresses a specific aspect of chat session access or knowledge indexing, and none feel redundant or unnecessary.

    Completeness4/5

    The tool set covers the core lifecycle of knowledge indexing (start, cancel, status, read artifacts) and session discovery/reading. Minor gaps include no ability to list all indexes at a high level (only batches) and no explicit session deletion, but these are not critical for the server's apparent purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources