Skip to main content
Glama

Related Servers

Alternatives to Harpyja

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that turns a task, error or stack trace into a few verbatim, line-cited source excerpts from a local repository index, staying inside a token budget the caller chooses. It also exposes tools to expand a cited range, outline or importance-rank a repository, and explore an import/reference graph, so coding agents can answer questions without reading whole files and without network or model calls.
      475 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Agent-safe code retrieval MCP server that indexes repositories and provides semantic search, file navigation, call graph analysis, and bounded file reading tools for coding agents.
      7,358,368 npm
      3
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that indexes reference repositories and provides tools for AI coding agents to retrieve lossless code context, enabling reasoning over codebases larger than the agent's context window.
      8
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Semantic + lexical code search as an MCP server. Agents query in natural language and get back ranked file:line ranges to read precisely.
      15 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local hybrid-search MCP server that enables coding agents to query files and folders using natural language, returning relevant code chunks with exact source paths. Everything runs on-device with no API keys or network calls.
      9
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      This MCP server enables coding agents to retrieve code across the whole machine through task briefings, exact file and line locations, grounded answers, dependency lookups, session guidance, and status checks, while reporting corrections and knowledge gaps to a separate retrieval engine.
      10
      MIT

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: building an index, locating relevant files/lines, and reading code snippets. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent pattern: 'harpyja_' prefix followed by a single verb (index, locate, read), ensuring predictability.

    Tool Count4/5

    With only 3 tools, the surface is minimal but well-scoped for the server's focused purpose of code indexing and retrieval. Slightly low, but not inappropriate.

    Completeness4/5

    The tool set covers the core workflow of building an index, searching, and reading code. Minor gaps exist (e.g., no directory listing), but it's sufficient for the intended use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues