Skip to main content
Glama

Related Servers

Alternatives to Open Kioku

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      A persistent, Git-versioned map of your whole codebase and database schema that coding agents read before they touch anything. Local-first MCP server + CLI in Go: a governed repository index of code knowledge that gives Claude Code, Codex, Cursor, and opencode long-term context, memory, and code intelligence.
      9
      1,815
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local-first codebase intelligence layer for AI coding agents, providing a persistent, queryable model of a repository via an MCP server and CLI to enable structure queries instead of reading many files.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local code intelligence for AI agents and editors by indexing source code, dependencies, Git history, tests, and documentation, and provides change-impact analysis and relevant test selection through MCP.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Persistent codebase knowledge layer for AI agents. Pre-digests codebases into structured knowledge (symbols, dependency graphs, co-change patterns, architectural decisions) and serves via MCP. 28 languages, 14 tools, ~85% token reduction.
      3 npm
      10
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Local-first code intelligence for AI coding assistants: MCP tools, symbol graph search, impact analysis, and auto-index watch for Cursor, Claude Code, and Codex.
      62
      2
      Business Source 1.1

    TDQS

    A4.1/5.0

    Scored across 42 tools

    Disambiguation4/5

    Most tools have distinct purposes with detailed descriptions including 'use this not that' guidance. However, with 42 tools, there is inherent overlap in categories like search and context building, which could still cause misselection despite clear documentation.

    Naming Consistency4/5

    Tool names consistently use underscores and mostly follow a verb_noun pattern (e.g., list_files, search_code, explain_symbol). Some noun-verb combinations (e.g., architecture_boundaries) still convey clear meaning, but the pattern is not perfectly uniform.

    Tool Count3/5

    42 tools is well above the typical 15-tool threshold for 'heavy' sets. While the server covers a broad domain (architecture, search, analysis, change management), many tools are granular and could be consolidated, making the count feel excessive.

    Completeness4/5

    The tool surface covers indexing, search, symbols, dependencies, architecture policy, context building, change planning, verification, and memory. Notable gaps include the absence of an apply_patch tool and limited execution capabilities, but core workflows are well-covered.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive