Skip to main content
Glama
jenkeeri
by jenkeeri

Related Servers

Alternatives to opengrok-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to query OpenGrok for source code searches, including definitions, symbols, and project listings, returning clickable URLs.
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding agents with structured access to indexed codebases via semantic search, symbol analysis, and file reading tools.
      13
      Server Side Public , v 1
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to search an index of open source repos and tools by what they do, their callable interface (MCP, CLI, SDK, API, etc.) and OG score, plus fetch repo details, category listings, and weekly trending projects.
      4
      0
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform high-performance code search and analysis across multiple languages using symbol indexing, regex text search, and structural AST pattern matching. It also provides tools for technology stack detection and dependency analysis with persistent caching for optimized performance.
      9
      MIT

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct action: search content, read a file, find files by path, list projects. The only overlap is that opengrok_search's 'path' parameter can also filter by path, which could be confused with opengrok_find_file, but the descriptions clarify that search returns matching lines while find_file returns only paths.

    Naming Consistency4/5

    All tools use the opengrok_ prefix and snake_case. Three follow verb_noun (get_file, find_file, list_projects), while search is just a verb, a minor deviation from the otherwise consistent pattern.

    Tool Count5/5

    Four tools is well-scoped for a read-only code search server. Each tool has a clear, non-redundant role: search content, retrieve file contents, find files, and list projects.

    Completeness4/5

    The core read-only workflows (search, read, find, list projects) are covered. Minor gaps exist, such as no direct file history/blame tool and no explicit directory listing beyond find_file patterns, but agents can work around these with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues