Open Kioku
Related Servers
Alternatives to Open Kioku
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA 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
- AlicenseNot gradedqualityDmaintenancePersistent 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.14 npm8MIT
- FlicenseBqualityBmaintenanceLocal-first code intelligence for AI coding assistants: MCP tools, symbol graph search, impact analysis, and auto-index watch for Cursor, Claude Code, and Codex.622-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.9 npm3MIT
- AlicenseNot gradedqualityAmaintenanceA local code-intelligence engine for AI agents that indexes repositories into a PostgreSQL-backed code graph and serves structured, token-budgeted context over MCP and HTTP, enabling targeted queries on symbols, dependencies, contracts, and impact analysis.Apache 2.0
- AlicenseCqualityAmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.76150 PyPI68MIT
TDQS
Scored across 42 tools
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.
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.
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.
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.