Skip to main content
Glama
jbacalso24

io.github.jbacalso24/mimry

by jbacalso24

Related Servers

Alternatives to io.github.jbacalso24/mimry

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding assistants with deep, semantic understanding of local codebases via AST-aware chunking, cross-repo symbol graphs, and architectural memory, enabling context-aware code search and dependency tracing.
      11
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Gives coding agents a memory of codebases by searching repositories using semantic similarity and structural call/import graphs, enabling reuse of proven patterns and reducing token usage.
      6
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to semantically search and navigate code repositories using natural language, with support for multiple repos, incremental indexing, and no local install needed.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to search, route, and read code across multiple repositories through a central semantic index, without needing to clone repositories locally.
      -

    TDQS

    C2.5/5.0

    Scored across 22 tools

    Disambiguation3/5

    Several tools occupy overlapping search/context/ranking territory, including find, semantic, related, symbol, path, why, explain, context, route, brief, and preflight. The descriptions clarify some boundaries, but the set still leaves meaningful ambiguity about which retrieval/explanation tool to choose.

    Naming Consistency4/5

    All tools use a consistent mimry_ prefix with lower_snake_case naming. The main variation is noun vs. verb forms such as mimry_status, mimry_find, and mimry_plan_tree, but the convention is still readable and predictable.

    Tool Count3/5

    The server exposes 22 tools, which is heavy for an MCP surface even considering the indexing, routing, and planning scope. It sits in the borderline-heavy range where consolidation or stronger grouping would improve usability.

    Completeness4/5

    The toolset covers index lifecycle, search, semantic retrieval, routing, context generation, explanations, feedback, digests, and plan tree operations. Minor gaps may exist around explicit reset/delete or plan mutation, but core workflows appear well represented.

    Maintenance

    ActivityActive
    ResponsivenessNo issues