Skip to main content
Glama

Related Servers

Alternatives to reprox-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides coding agents with persistent repository context, including code maps, specs, timeline, team memory, and past session history, through MCP tools.
      265 PyPI
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to retrieve compact, cited repository maps through MCP tools such as search, symbol inspection, flow investigation, and deep context loading.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.
      24 PyPI
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to retrieve and manage code context with hybrid search, project memory, and observability via MCP tools.
      29
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to persistently store and retrieve conversation history with hybrid semantic and keyword search, cross-encoder reranking, session filtering, and archiving through MCP tools.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent memory for AI coding agents, enabling them to save, search (hybrid vector/BM25/concept graph), list sessions, and forget memories via MCP tools.
      11 npm
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: search for context, list/get gaps, get related memories, get architecture, and get timeline. Overlap with the generic search is acceptable because the specific getters are clearly scoped to particular memory types.

    Naming Consistency4/5

    All tool names use snake_case and an imperative verb prefix like search_, list_, or get_. The only minor deviation is get_related, which uses an adjective rather than a clear noun object, but the pattern remains highly predictable.

    Tool Count5/5

    With six tools, the server is well-scoped for a repository-context memory retrieval service. Each tool covers a meaningful access pattern without unnecessary redundancy or bloat.

    Completeness5/5

    The tool surface covers the full read-only retrieval lifecycle: broad search, specific gap lookup, relationship traversal, architecture overview, and timeline/history access. No significant missing operation is apparent for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues