A
licenseNot graded
qualityA
maintenanceSupercharge your Agent with Semantic Code Intelligence
and save 💰 in the process!
681
MIT
Kivgraph
by Luqueee
Related Servers
Alternatives to Kivgraph
- AlicenseAqualityDmaintenanceDeterministic code review MCP server that provides tools for file selection, rule matching, comment positioning, and reflection, ensuring stable review quality without LLM calls.511 npm1MIT
CodeGraphofficial
AlicenseNot gradedqualityAmaintenanceBuilds a semantic graph of codebases across 38 languages and exposes 42 MCP tools for structured code understanding, search, and impact analysis.134Apache 2.0
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query and analyze code across multiple repositories through a unified knowledge graph, with tools for symbol search, impact analysis, and graph algorithms.15 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic code search across multiple repositories using natural language queries. Provides intelligent code discovery, symbol lookups, and cross-repo dependency analysis for AI coding agents.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search code, inspect symbols, navigate call graphs, and analyze change impact across scoped local repositories through the same engine as the CLI and REST API.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to query a codebase as a graph, retrieving definitions, callers, callees, dependencies, and focused context so they fetch only the code they need instead of reading whole repositories.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a local structural code graph for focused context, including relevant source entities, Git relationships, call paths, impact, and recorded mistakes. It exposes this context so agents can investigate code and retrieve bounded context before reading full files.24 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables developer agents to perform semantic codebase search, dependency and impact analysis, cross-file refactoring, and full-stack API tracing through a unified query DSL over a high-performance graph engine.-
TDQS
A3.5/5.0
Scored across 12 tools
Disambiguation4/5
Each tool targets a distinct query type—semantic search, identifier search, symbol metadata, reference/consumer lookup, forward/reverse graph traversal, and index administration—but get_blast_radius vs trace_dependencies and find_references vs find_cross_repo_consumers are close enough that an agent must read descriptions carefully to pick correctly.
Naming Consistency4/5
Most tools follow a verb_noun pattern (find_*, get_*, list_repositories, index_project, trace_dependencies), forming clear families for search and retrieval. graph_status is the notable outlier, reading as a noun phrase rather than a verb-object command.
Tool Count5/5
Twelve tools is well within the ideal range for a code-intelligence server, and each tool earns its place: symbol search, references, cross-repo consumers, dependency/impact analysis, source/outline retrieval, and index administration. None of the tools feels redundant.
Completeness4/5
The surface covers discovery, metadata, source/outline retrieval, references/consumers, dependency and blast-radius analysis, plus index status and registration, so core workflows are well supported. Minor gaps exist around arbitrary file-content reads and project removal or re-indexing semantics, but agents can work around them.
Maintenance
ActivitySlowing
ResponsivenessResponsive