Skip to main content
Glama

Related Servers

Alternatives to LLMScribe

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides coding agents with repository-aware tools to understand code structure, find existing patterns, and review plans, architecture, and diffs, enabling a consistent engineering workflow across Cursor, Codex, and Claude Code.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables language models to explore and analyze source code repositories through read-only tools for listing directories, reading files, searching code, finding symbols, and inspecting git history, with strict sandboxing and security controls.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants to inspect local and remote repositories through sandboxed tools that surface project overviews, structure, dependency audits, Git churn hotspots, and a heuristic health score. It also supports safe GitHub issue searching and creation with built-in duplicate preflight checks, while blocking sensitive files, binary content, and path traversal attacks.
      22 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to safely read, search, understand, and edit local project code and files, with Git inspection, code indexing, and controlled command execution within permissioned workspaces.
      4 npm
      6
      MIT

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are cleanly separated by purpose: search vs read vs read_many vs project_diff are unambiguous. The one soft overlap is project_map vs project_overview, which both return a directory tree, though the descriptions make the contents-vs-no-contents distinction explicit. project_dependencies is clearly distinct in output shape.

    Naming Consistency3/5

    All names are snake_case, but the convention is applied unevenly: some carry a project_ prefix (project_map, project_overview, project_dependencies, project_diff) while the core file operations are bare verbs (search, read, read_many). Readable, but an agent can't infer the prefix rule predictably.

    Tool Count5/5

    Seven tools is well within the ideal range and each one earns its place: three discovery tools, two read tools, a dependency tool, and a diff tool. No redundant or filler entries.

    Completeness4/5

    The read-only exploration lifecycle is largely covered: map, bulk overview, search, single/bulk read, dependency graph, and git diff. Minor gaps remain, such as no line-range or offset read for large files and no pattern/glob filtering when listing files, all of which agents can work around with search.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues