Skip to main content
Glama

Related Servers

Alternatives to Context Grove

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to query a team's institutional coding rules and lessons learned, resolving a project → framework → language → global scope hierarchy so only the entries relevant to the current task are returned instead of whole knowledge-base files. It also supports governed proposal approval, PR and feature audits, meeting-transcript extraction, optional semantic ranking, and access-controlled audit logging, while keeping Markdown files as the source of truth.
      28
      21 PyPI
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Lets AI agents query, search and read wiki pages and raw transcripts of past coding sessions, so they can look up prior decisions and fixes before redoing work. It also exposes linting, sync, export and dashboard tools over stdio, with path-traversal guards and no SDK dependency.
      15
      441 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, read, create, patch, lint, and synchronize a shared Markdown+git knowledge base across multiple machines and sessions, with confidence metadata and protocol resources.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to query a local code graph over stdio, so they can see what a Git change may affect, find related tests, routes and nodes, and cite evidence paths — read-only and fully on-machine.
      2 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: availability check, catalog listing, document reading, and text search. There is no meaningful overlap between health, catalog, read, and search in this read-only knowledge context.

    Naming Consistency5/5

    All tool names follow the same predictable snake_case pattern with a shared knowledge_ prefix. The suffixes vary between resource and action words, but the overall convention is consistent and readable.

    Tool Count5/5

    Four tools are well-scoped for a read-only project knowledge source. Each tool earns its place by covering a distinct part of the access lifecycle: availability, discovery, retrieval, and search.

    Completeness5/5

    The surface covers checking availability, listing canonical areas and documents, reading by path, and searching with cited snippets. For a read-only knowledge access interface, this is complete with no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues